Contact

Talk to a person.

Four subjects, each with the address that handles it. Pick the one that matches and the subject line will already be filled in — that is what gets your message to the right place first time.

Customer support

An environment that will not start, a build that fails, a restore you need help with. Write from the address on your account so we can find your team without asking.

Questions before signing up

Pricing for a specific setup, whether your modules will build, what reselling to your own clients involves, or a walkthrough of the platform.

Report a vulnerability

Security reports are read first. The disclosure policy, including what is in scope and the good-faith protections that come with it, is on the security page.

Privacy and data requests

Access, correction, export or deletion of personal data, and questions about how it is processed. If your account was created by an integrator, tell us which one.

Getting a faster answer

Most of the back-and-forth on a support thread is us asking which environment you mean. Including these turns two days into one reply:

  • The instance and environment name, or the URL you are seeing the problem on.
  • What you expected, what happened, and the time it happened — with a timezone.
  • The exact error text, rather than a description of it.
  • Whether it happens every time or intermittently, and when it last worked.

What to expect

We read everything and answer as quickly as we can. We do not publish a response time, because outside a signed support agreement none is owed and a number nobody is accountable for is worth nothing to you. Vulnerability reports are the exception: they go to the front of the queue.