Enterprise and procurement
A dedicated deployment in a region you name, operated by us, plus security questionnaires and procurement documentation.
enterprise@enclessa.appContact
Most questions are answered on the pricing, security and FAQ pages, and reading those first will get you a better answer faster. For an Enterprise arrangement, a dedicated deployment, a procurement questionnaire or a security report, use the route below that fits.
Open betaThe platform is being built in the open, so parts of it are not there yet, behaviour changes between releases, and no availability figure is committed while it is in beta. What is still being built.
A dedicated deployment in a region you name, operated by us, plus security questionnaires and procurement documentation.
enterprise@enclessa.appYou already have a workspace and something is not working. Include your workspace address so it can be found.
support@enclessa.appReport a vulnerability privately rather than in a public issue. You will get an acknowledgement and a timeline.
security@enclessa.appQuestions about the data processing agreement, sub-processors, or a data-subject request.
privacy@enclessa.appFour questions account for most of the post, and each has a page that answers it in more detail than an email will:
If you do write, three lines save a week: which of the routes above you are on, your workspace address if you have one, and what you are trying to decide rather than only what you are asking. A procurement questionnaire is answered faster with the deadline stated in the first message than in the fourth.
Enclessa is in open beta and there is no contractual response time on any of these addresses; what there is instead is that they are read by the people who build the platform, and a security report is acknowledged before it is investigated.
Legal and provider details are on the imprint.