Architecture and Integration

Integration Methods

The new Stripo editor is built on a microservices architecture, effectively combining front-end and back-end components.

Understanding the diverse needs of our users, we offer two main ways to use the editor:

1. Standard mode: The entire editor infrastructure is deployed on Stripo’s servers. This is an ideal choice for those who value quick implementation and convenience without additional costs.

   Advantages:

   • ease of implementation;
   • cost-effective solution.

   Disadvantages:

   • data storage on Stripo's side, which may not comply with the data retention policies of some organizations; however, the data is hosted in a secure manner as we follow GDPR and are SOC2 compliant. Our servers are hosted with AWS in the Ireland region.
   • limited opportunities for customizing infrastructure capabilities.

2. Extended mode: The ability to deploy the editor's infrastructure on the client's servers, providing full control and flexible management. This option is possible only with Enterprise plan.

   Advantages:

   • data privacy due to storage on the client's side;
   • full control and flexible management of the infrastructure.

   Disadvantages:

   • higher solution cost;
   • the need for the client's DevOps team to set up and maintain the infrastructure (Stripo is ready to provide engineers to assist in deployment or consult the client's team).

These integration methods offer clients flexibility in choosing based on their technical requirements and business needs, allowing for the optimal use of the editor.

Email Storage and Synchronization

The new Stripo editor is designed for reliable data storage, effective conflict resolution during simultaneous editing by multiple users, and flexible user rights management for working with an email. Unlike the old editor, where emails were transferred to the client’s environment via webhook, the decision was made to store emails in Plugins’s database. This ensures that editor always maintains a “reference email” that can be edited simultaneously by multiple users.

Stripo retains the ability to receive information about changes to an email via webhook.

However, from now on, this will only include data about the time of the change and the user identifier. Once the webhook is received, the plugin customer may send a request from their server to the Stripo server here to get the HTML and CSS to securely store on their end the most updated version of the template.

Key aspects of working with the editor:

• if a new email is created, the provided HTML and CSS parameters will create a “reference email” in Stripo’s database, which users will then begin to work on;
• if a user joins an email that is already being edited by others, the provided HTML and CSS parameters are ignored, and the user will be connected to editing the “reference email”;
• replacing the “reference email” can only be done when no one is working on the email in the editor. During editor initialization, besides the HTML and CSS parameters, a special additional parameter forceRecreate: true must be provided (see the table of all parameters).
• The compiled version of email can be retrieved with GET request to Stripo server here.