Support Policy

Which channels, response times and scope your support has, by plan.

Support channels

The support channel available to you depends on your plan:

  • Free: documentation at docs.html and GitHub Discussions. No email support.
  • Builder: email to support@vericto.com.
  • Team: priority email to support@vericto.com.
  • Enterprise: private Slack channel (or Microsoft Teams on Premium) + email + emergency phone line.

Every plan, without exception, has access to security@vericto.com to report security vulnerabilities, regardless of the plan.

Coverage by plan

The table below summarises channels, hours and first-response SLA by plan:

Response times

Incidents are classified by priority according to their impact on the service:

  • P1: production down: the service is unavailable or enforcement data cannot reach Vericto, with no workaround.
  • P2: major degradation: a critical function is degraded.
  • P3: minor issue, or a workaround exists.
  • P4: question or request.

Enterprise: support by SLA tier

On Enterprise, support depends on the plan in your contract: Standard (99.9% SLA, on shared infrastructure), Enhanced (99.95%, with a dedicated deployment) or Premium (99.99%, with a dedicated multi-region deployment). Times are first-response targets, not resolution times. Business hours are Monday to Friday, 9:00 to 18:00, in the customer's time zone set in the Order Form.

What is covered

Vericto support covers the following areas:

  • Integrating the TCP proxy with your database.
  • Configuring standard and custom AST rules.
  • Using the Vericto CLI/SDK.
  • Problems in the Vericto dashboard.
  • Billing and plan changes.
  • Configuring Slack alerts and webhooks.

What is not covered

Vericto support is limited to the use of the service itself. The following fall outside the scope of support:

  • Internal code of the customer's application.
  • Configuration and administration of the customer's database.
  • Bugs in third-party drivers or ORMs.
  • General architecture consulting unrelated to Vericto.
  • Incidents caused by misconfigured customer credentials.

Escalation process

If an incident is not resolved within the expected time, the escalation process is as follows:

  1. Contact support@vericto.com with a description of the problem, the estimated priority and steps to reproduce it.
  2. If there is no resolution within the applicable SLA, the ticket is escalated automatically to the engineering team.
  3. For active P1 incidents without resolution, it escalates directly to the CTO.

Incidents affecting multiple customers get a public post-mortem on the Vericto status page once resolved.

Security support

security@vericto.com is available on every plan, including Free. Initial response time is 48 hours at most, regardless of business hours.