Docs

Alerts and webhooks

Read alerts, tune the rules that create them, and register webhooks that receive them, signed and retried.

Applies to EngineCloud At launch

View as Markdown
On this page
  1. The alert object
  2. The webhook object
  3. What a webhook receives
  4. Check the signature
  5. Take the raw body
  6. Compute the signature
  7. Compare, and check the time
  8. Retries
  9. List alerts
  10. Get an alert
  11. Acknowledge an alert
  12. List alert rules
  13. Update an alert rule
  14. List webhooks
  15. Create a webhook
  16. Get a webhook
  17. Update a webhook
  18. Delete a webhook
  19. List a webhook’s deliveries
  20. Send a test event

An alert is a record that says something needs a person: a new problem, a problem that came back, your app not answering. The engine always records alerts. What happens next depends on where you run:

The Sypnia engine and Sypnia Cloud compared
Sypnia engineOpen source, self-hostedSypnia CloudPaid service, with a free tier
Recorded; listed by API, MCP and CLIYesYes
Sent to your webhooksYesYes
E-mailNo. The default deployment has no e-mail sender. See the guideYes
Shown to peopleIn the ConsoleIn the app

Alerts are created for the production environment only, unless you change a rule’s environments. There is no integration with chat apps: a webhook is the way to send an alert anywhere else.

A self-hosted engine can also send every alert of every project to one URL, without any call to this API: set SYPNIA_ALERT_WEBHOOK_URL. See the configuration reference.

The alert object

Fields

  • id
    string optional

    alt_….

  • kind
    string optional

    Which rule created it. See the alert rules.

  • title
    string optional

    The alert in one line, ready to send to a person.

  • environment
    string optional
  • subject
    object optional

    What the alert is about.

  • subject.type
    string

    One of: problem, uptime_check, page, api_route, project.

  • subject.id
    string

    The problem’s or check’s id, or the route.

  • subject.slug
    string

    Problems only.

  • created_at
    timestamp optional
  • acknowledged_at
    timestamp or null optional
  • acknowledged_by
    string or null optional

    Who acknowledged it, written like resolved_by on a problem.

  • url
    URL optional

    Where to look, in the app or the Console.

The webhook object

Fields

  • id
    string optional

    whk_….

  • url
    URL optional
  • events
    array of string optional
  • enabled
    boolean optional
  • created_at
    timestamp optional
  • last_delivery
    object or null optional

    The latest delivery and how it went.

  • disabled_reason
    string or null optional

    failing when the engine switched it off after 3 days of failed deliveries.

What a webhook receives

Each event is one POST to your URL with a JSON body.

Event typeWhen
alert.createdAn alert was created. This is the one to forward to people
problem.createdA problem was seen for the first time, in any environment
problem.analyzedThe agent finished an analysis. data.problem.analysis has it
problem.status_changedA problem was resolved, reopened, ignored, or came back
problem.pull_request_openedSypnia Cloud only: Sypnia opened a pull request
pingYou created the webhook, or asked for a test

Headers of a delivery

HTTP
POST /hooks/sypnia HTTP/1.1
Content-Type: application/json
User-Agent: Sypnia-Webhooks/1.0
Sypnia-Event: alert.created
Sypnia-Delivery: dlv_2s4d6f8g0h1j
Sypnia-Attempt: 1
Sypnia-Signature: t=1773306783,v1=5257a869e7ecebeda32affa62cdca3fa51cad7e77a0e56ff536d0ce8e108d8bd

Body of an `alert.created` delivery

JSON
{
  "id": "evt_7m3n9b5v1c8x",
  "type": "alert.created",
  "created_at": "2026-03-12T09:13:02Z",
  "project": { "id": "prj_5k2m9x4q7w1z", "slug": "shop", "name": "Shop" },
  "data": {
    "alert": {
      "id": "alt_6w2e8r4t1y9u",
      "kind": "problem.new",
      "title": "New problem: 1 person tried to pay and could not.",
      "environment": "production",
      "subject": { "type": "problem", "id": "prb_8f3k2m9x4q7w", "slug": "pay-button-does-nothing" },
      "created_at": "2026-03-12T09:13:02Z",
      "acknowledged_at": null,
      "acknowledged_by": null,
      "url": "https://app.sypnia.com/shop/problems/pay-button-does-nothing"
    },
    "problem": {
      "id": "prb_8f3k2m9x4q7w",
      "slug": "pay-button-does-nothing",
      "status": "open",
      "title": "createPayment answered 400 in POST /api/checkout",
      "sentence": null,
      "people": 1,
      "sessions": 1,
      "first_seen": "2026-03-12T09:12:04Z",
      "url": "https://app.sypnia.com/shop/problems/pay-button-does-nothing"
    }
  }
}

Fields of every delivery

  • id
    string

    The event’s id, evt_…. It is the same on every retry of the same event: store it and ignore an id you have already handled.

  • type
    string

    The event type, as in the table above. Also in the Sypnia-Event header.

  • created_at
    timestamp

    When the event happened, not when it was sent.

  • project
    object

    The project: id, slug, name.

  • data
    object

    For alert.created: alert, plus problem or check when the alert is about one. For the problem.* types: problem, in the short form above, plus previous_status for problem.status_changed. For ping: empty. An alert sent in the first 2 minutes of a problem may have sentence set to null: the alert does not wait for the agent beyond that.

Check the signature

Anyone who learns your URL can post to it. Check that a delivery comes from Sypnia before you act on it.

Sypnia-Signature has a timestamp t (seconds) and a signature v1. The signature is the HMAC-SHA256, in hex, of the timestamp, a dot and the raw body, keyed with the webhook’s secret (whsec_…).

  1. Take the raw body

    Read the body as bytes, before any JSON parsing. A parsed and re-written body will not match.

  2. Compute the signature

    Compute HMAC-SHA256(secret, t + "." + raw body) and write it in hex.

  3. Compare, and check the time

    Compare with v1 using a constant-time comparison. Reject the delivery when they differ, or when t is more than 5 minutes from your clock, which stops an old delivery from being replayed.

Node.js

verify.js
import { createHmac, timingSafeEqual } from 'node:crypto';

export function isFromSypnia(rawBody, header, secret) {
  const parts = Object.fromEntries(header.split(',').map((p) => p.split('=')));
  if (!parts.t || !parts.v1) return false;
  if (Math.abs(Date.now() / 1000 - Number(parts.t)) > 300) return false;

  const expected = createHmac('sha256', secret).update(`${parts.t}.${rawBody}`).digest('hex');
  const a = Buffer.from(expected);
  const b = Buffer.from(parts.v1);
  return a.length === b.length && timingSafeEqual(a, b);
}

Retries

A delivery succeeds when your receiver answers any 2xx within 10 seconds. Answer first, then do slow work.

Anything else is retried, with the same evt_… id and a higher Sypnia-Attempt:

AttemptWhen
1At once
21 minute later
35 minutes later
430 minutes later
52 hours later
66 hours later
712 hours later

After the seventh failure the delivery is failed and is not tried again. When every delivery to a webhook has failed for 3 days, the engine switches the webhook off (disabled_reason is failing) and creates an engine.failing alert. Switch it back on with PATCH.

Deliveries may arrive out of order and, rarely, twice. Use the event’s id to ignore duplicates and created_at to order.

List alerts

GET /v1/alerts EngineCloud

Alerts created in the time range, newest first.

Authentication
API token (read)

Query parameters

  • project
    string optional

    The project’s id or slug. Needed only with a credential that can see several projects (the root token). With an API token it is ignored unless it names another project, which is 403.

  • kind
    string optional

    Only alerts of this kind. See the alert rules for the list.

  • acknowledged
    boolean optional

    false returns only alerts nobody has acknowledged.

  • since
    string optional

    Only alerts created after this moment.

    Default: 7d

  • until
    string optional

    End of the time range. An ISO 8601 timestamp or a relative value. Defaults to now.

  • limit
    integer, 1 to 200 optional

    Most items to return.

    Default: 50

  • cursor
    string optional

    The next_cursor of the previous page. Keep every other parameter the same.

Request

Terminal
curl "https://api.sypnia.com/v1/alerts?acknowledged=false" \
  -H "Authorization: Bearer $SYPNIA_API_TOKEN"

Response200

JSON
{
  "data": [
    {
      "id": "alt_6w2e8r4t1y9u",
      "kind": "problem.new",
      "title": "New problem: 1 person tried to pay and could not.",
      "environment": "production",
      "subject": {
        "type": "problem",
        "id": "prb_8f3k2m9x4q7w",
        "slug": "pay-button-does-nothing"
      },
      "created_at": "2026-03-12T09:13:02Z",
      "acknowledged_at": null,
      "acknowledged_by": null,
      "url": "https://app.sypnia.com/shop/problems/pay-button-does-nothing"
    }
  ],
  "next_cursor": null
}

Get an alert

GET /v1/alerts/{alert_id} EngineCloud

One alert.

Authentication
API token (read)

Path parameters

  • alert_id
    string required

    The alert’s id (alt_…).

Query parameters

  • project
    string optional

    The project’s id or slug. Needed only with a credential that can see several projects (the root token). With an API token it is ignored unless it names another project, which is 403.

Request

Terminal
curl "https://api.sypnia.com/v1/alerts/alt_6w2e8r4t1y9u" \
  -H "Authorization: Bearer $SYPNIA_API_TOKEN"

Response200

JSON
{
  "id": "alt_6w2e8r4t1y9u",
  "kind": "problem.new",
  "title": "New problem: 1 person tried to pay and could not.",
  "environment": "production",
  "subject": {
    "type": "problem",
    "id": "prb_8f3k2m9x4q7w",
    "slug": "pay-button-does-nothing"
  },
  "created_at": "2026-03-12T09:13:02Z",
  "acknowledged_at": null,
  "acknowledged_by": null,
  "url": "https://app.sypnia.com/shop/problems/pay-button-does-nothing"
}

Errors

  • 404not_found

    No alert has this id in the project.

Acknowledge an alert

POST /v1/alerts/{alert_id}/acknowledge EngineCloud

Records that someone saw the alert. It changes nothing else, the problem or check behind it keeps its status. Acknowledging twice answers 200 and keeps the first acknowledgement.

Authentication
API token (read)

Path parameters

  • alert_id
    string required

    The alert’s id (alt_…).

Query parameters

  • project
    string optional

    The project’s id or slug. Needed only with a credential that can see several projects (the root token). With an API token it is ignored unless it names another project, which is 403.

Request

Terminal
curl -X POST "https://api.sypnia.com/v1/alerts/alt_6w2e8r4t1y9u/acknowledge" \
  -H "Authorization: Bearer $SYPNIA_API_TOKEN"

Response200

JSON
{
  "id": "alt_6w2e8r4t1y9u",
  "kind": "problem.new",
  "title": "New problem: 1 person tried to pay and could not.",
  "environment": "production",
  "subject": {
    "type": "problem",
    "id": "prb_8f3k2m9x4q7w",
    "slug": "pay-button-does-nothing"
  },
  "created_at": "2026-03-12T09:13:02Z",
  "acknowledged_at": "2026-03-12T10:36:20Z",
  "acknowledged_by": "token:Cursor",
  "url": "https://app.sypnia.com/shop/problems/pay-button-does-nothing"
}

Errors

  • 404not_found

    No alert has this id in the project.

List alert rules

GET /v1/alert-rules EngineCloud

The rules that create alerts. The set is fixed: there is one rule per kind of alert, and you switch each one on or off and tune its thresholds. You cannot add kinds.

KindCreates an alert whenThresholds (defaults)
problem.newA problem is seen for the first timeNone
problem.regressedA resolved problem happens againNone
problem.growingAn open problem reaches twice the people it had at its last alertfactor 2, min_people 5
uptime.downA check fails twice in a rowfailures 2
uptime.recoveredA check that was down answers againNone
page.slowerA page’s LCP at p75 over the last 24 hours grew against the 7 days beforeincrease_percent 30, min_views 50
api.failingAn API route answers 5xx or nothing too often over the last hourerror_rate_percent 2, min_requests 50
usage.limitThe project reaches a share of a usage limitpercents 80 and 100
engine.failingProcessing has not caught up for 30 minutes, or webhook deliveries keep failingNone
Authentication
API token (read)

Query parameters

  • project
    string optional

    The project’s id or slug. Needed only with a credential that can see several projects (the root token). With an API token it is ignored unless it names another project, which is 403.

Request

Terminal
curl "https://api.sypnia.com/v1/alert-rules" \
  -H "Authorization: Bearer $SYPNIA_API_TOKEN"

Response200

JSON
{
  "data": [
    {
      "kind": "problem.new",
      "enabled": true,
      "environments": [
        "production"
      ],
      "thresholds": {}
    },
    {
      "kind": "problem.regressed",
      "enabled": true,
      "environments": [
        "production"
      ],
      "thresholds": {}
    },
    {
      "kind": "problem.growing",
      "enabled": true,
      "environments": [
        "production"
      ],
      "thresholds": {
        "factor": 2,
        "min_people": 5
      }
    },
    {
      "kind": "uptime.down",
      "enabled": true,
      "environments": [
        "production"
      ],
      "thresholds": {
        "failures": 2
      }
    },
    {
      "kind": "uptime.recovered",
      "enabled": true,
      "environments": [
        "production"
      ],
      "thresholds": {}
    },
    {
      "kind": "page.slower",
      "enabled": true,
      "environments": [
        "production"
      ],
      "thresholds": {
        "increase_percent": 30,
        "min_views": 50
      }
    },
    {
      "kind": "api.failing",
      "enabled": true,
      "environments": [
        "production"
      ],
      "thresholds": {
        "error_rate_percent": 2,
        "min_requests": 50
      }
    },
    {
      "kind": "usage.limit",
      "enabled": true,
      "environments": [
        "production"
      ],
      "thresholds": {
        "percents": [
          80,
          100
        ]
      }
    },
    {
      "kind": "engine.failing",
      "enabled": true,
      "environments": [
        "production"
      ],
      "thresholds": {}
    }
  ]
}

Update an alert rule

PATCH /v1/alert-rules/{kind} EngineCloud

Switches a rule on or off, changes the environments it watches, or changes its thresholds. Send only what changes; thresholds are merged key by key.

Authentication
API token (admin)

Path parameters

  • kind
    string required

    The rule’s kind, for example page.slower. One of: problem.new, problem.regressed, problem.growing, uptime.down, uptime.recovered, page.slower, api.failing, usage.limit, engine.failing.

Query parameters

  • project
    string optional

    The project’s id or slug. Needed only with a credential that can see several projects (the root token). With an API token it is ignored unless it names another project, which is 403.

Body

  • enabled
    boolean optional

    false stops this kind of alert.

  • environments
    array of string optional

    The environments the rule watches.

  • thresholds
    object optional

    The thresholds to change, by name. See the table of rules.

Request

Terminal
curl -X PATCH "https://api.sypnia.com/v1/alert-rules/page.slower" \
  -H "Authorization: Bearer $SYPNIA_ADMIN_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"thresholds": {"increase_percent": 50}}'

Response200

JSON
{
  "kind": "page.slower",
  "enabled": true,
  "environments": [
    "production"
  ],
  "thresholds": {
    "increase_percent": 50,
    "min_views": 50
  }
}

Errors

  • 400invalid_request

    A threshold is unknown for this kind or out of range. param names it.

  • 404not_found

    No rule has this kind.

List webhooks

GET /v1/webhooks EngineCloud

The project’s webhooks. Secrets are not shown.

Authentication
API token (admin)

Query parameters

  • project
    string optional

    The project’s id or slug. Needed only with a credential that can see several projects (the root token). With an API token it is ignored unless it names another project, which is 403.

Request

Terminal
curl "https://api.sypnia.com/v1/webhooks" \
  -H "Authorization: Bearer $SYPNIA_ADMIN_TOKEN"

Response200

JSON
{
  "data": [
    {
      "id": "whk_4z6x8c2v0b1n",
      "url": "https://shop.example.com/hooks/sypnia",
      "events": [
        "alert.created",
        "problem.analyzed"
      ],
      "enabled": true,
      "created_at": "2026-02-02T09:25:00Z",
      "last_delivery": {
        "at": "2026-03-12T10:33:06Z",
        "status": "delivered",
        "response_status": 200
      },
      "disabled_reason": null
    }
  ],
  "next_cursor": null
}

Create a webhook

POST /v1/webhooks EngineCloud

Registers a URL of yours to receive events. The signing secret is in secret and is shown only in this answer. The URL must be https (a self-hosted engine also accepts http when SYPNIA_WEBHOOKS_ALLOW_HTTP is true, for a receiver inside your own network).

The engine sends a ping event right after creation, so you can see your receiver work.

Authentication
API token (admin)

Query parameters

  • project
    string optional

    The project’s id or slug. Needed only with a credential that can see several projects (the root token). With an API token it is ignored unless it names another project, which is 403.

Headers

  • Idempotency-Key
    string, up to 255 characters optional

    A value of your own, 1 to 255 characters, that makes the call safe to repeat. See idempotency.

Body

  • url
    URL, up to 2,000 characters required

    Where to send events.

  • events
    array of string optional

    The event types to send. problem.pull_request_opened only happens on Sypnia Cloud. One of: alert.created, problem.created, problem.analyzed, problem.status_changed, problem.pull_request_opened.

    Default: ['alert.created']

  • enabled
    boolean optional

    false creates it paused.

    Default: true

Request

Terminal
curl -X POST "https://api.sypnia.com/v1/webhooks" \
  -H "Authorization: Bearer $SYPNIA_ADMIN_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"url": "https://shop.example.com/hooks/sypnia", "events": ["alert.created", "problem.analyzed"]}'

Response201

JSON
{
  "id": "whk_4z6x8c2v0b1n",
  "url": "https://shop.example.com/hooks/sypnia",
  "events": [
    "alert.created",
    "problem.analyzed"
  ],
  "enabled": true,
  "secret": "whsec_Jt5nQ8rV2xZ7cB4mK9pL1dF6hS3gA0wE",
  "created_at": "2026-02-02T09:25:00Z",
  "last_delivery": null,
  "disabled_reason": null
}

Errors

  • 400invalid_request

    The URL is not https, resolves to a private address (Sypnia Cloud), or events has an unknown type.

  • 409limit_reached

    The project already has 10 webhooks.

Get a webhook

GET /v1/webhooks/{webhook_id} EngineCloud

One webhook, without its secret.

Authentication
API token (admin)

Path parameters

  • webhook_id
    string required

    The webhook’s id (whk_…).

Query parameters

  • project
    string optional

    The project’s id or slug. Needed only with a credential that can see several projects (the root token). With an API token it is ignored unless it names another project, which is 403.

Request

Terminal
curl "https://api.sypnia.com/v1/webhooks/whk_4z6x8c2v0b1n" \
  -H "Authorization: Bearer $SYPNIA_ADMIN_TOKEN"

Response200

JSON
{
  "id": "whk_4z6x8c2v0b1n",
  "url": "https://shop.example.com/hooks/sypnia",
  "events": [
    "alert.created",
    "problem.analyzed"
  ],
  "enabled": true,
  "created_at": "2026-02-02T09:25:00Z",
  "last_delivery": {
    "at": "2026-03-12T10:33:06Z",
    "status": "delivered",
    "response_status": 200
  },
  "disabled_reason": null
}

Errors

  • 404not_found

    No webhook has this id in the project.

Update a webhook

PATCH /v1/webhooks/{webhook_id} EngineCloud

Changes the URL, the events or enabled. Setting enabled to true on a webhook the engine disabled starts deliveries again. Send rotate_secret as true to get a new secret, shown only in this answer; the old one stops working at once.

Authentication
API token (admin)

Path parameters

  • webhook_id
    string required

    The webhook’s id (whk_…).

Query parameters

  • project
    string optional

    The project’s id or slug. Needed only with a credential that can see several projects (the root token). With an API token it is ignored unless it names another project, which is 403.

Body

  • url
    URL, up to 2,000 characters optional

    Where to send events.

  • events
    array of string optional

    The event types to send. Replaces the list.

  • enabled
    boolean optional

    false pauses deliveries; events that happen meanwhile are not sent later.

  • rotate_secret
    boolean optional

    true replaces the signing secret.

    Default: false

Request

Terminal
curl -X PATCH "https://api.sypnia.com/v1/webhooks/whk_4z6x8c2v0b1n" \
  -H "Authorization: Bearer $SYPNIA_ADMIN_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"events": ["alert.created"]}'

Response200

JSON
{
  "id": "whk_4z6x8c2v0b1n",
  "url": "https://shop.example.com/hooks/sypnia",
  "events": [
    "alert.created"
  ],
  "enabled": true,
  "created_at": "2026-02-02T09:25:00Z",
  "last_delivery": {
    "at": "2026-03-12T10:33:06Z",
    "status": "delivered",
    "response_status": 200
  },
  "disabled_reason": null
}

Errors

  • 404not_found

    No webhook has this id in the project.

Delete a webhook

DELETE /v1/webhooks/{webhook_id} EngineCloud

Deletes the webhook and stops its pending deliveries.

Authentication
API token (admin)

Path parameters

  • webhook_id
    string required

    The webhook’s id (whk_…).

Query parameters

  • project
    string optional

    The project’s id or slug. Needed only with a credential that can see several projects (the root token). With an API token it is ignored unless it names another project, which is 403.

Request

Terminal
curl -X DELETE "https://api.sypnia.com/v1/webhooks/whk_4z6x8c2v0b1n" \
  -H "Authorization: Bearer $SYPNIA_ADMIN_TOKEN"

Errors

  • 404not_found

    No webhook has this id in the project.

List a webhook’s deliveries

GET /v1/webhooks/{webhook_id}/deliveries EngineCloud

What was sent to the webhook and how your receiver answered, newest first. Deliveries are kept for 30 days. Use it to find out why an alert did not arrive.

Authentication
API token (admin)

Path parameters

  • webhook_id
    string required

    The webhook’s id (whk_…).

Query parameters

  • project
    string optional

    The project’s id or slug. Needed only with a credential that can see several projects (the root token). With an API token it is ignored unless it names another project, which is 403.

  • status
    string optional

    Only deliveries in this status. One of: pending, delivered, failed.

  • limit
    integer, 1 to 200 optional

    Most items to return.

    Default: 50

  • cursor
    string optional

    The next_cursor of the previous page. Keep every other parameter the same.

Request

Terminal
curl "https://api.sypnia.com/v1/webhooks/whk_4z6x8c2v0b1n/deliveries?status=failed" \
  -H "Authorization: Bearer $SYPNIA_ADMIN_TOKEN"

Response200

JSON
{
  "data": [
    {
      "id": "dlv_2s4d6f8g0h1j",
      "event_id": "evt_7m3n9b5v1c8x",
      "event_type": "alert.created",
      "status": "delivered",
      "attempts": 1,
      "response_status": 200,
      "response_ms": 142,
      "created_at": "2026-03-12T09:13:03Z",
      "delivered_at": "2026-03-12T09:13:03Z",
      "next_attempt_at": null,
      "error": null
    }
  ],
  "next_cursor": null
}

Errors

  • 404not_found

    No webhook has this id in the project.

Send a test event

POST /v1/webhooks/{webhook_id}/test EngineCloud

Sends a ping event to the webhook now, signed like a real one, and answers with what your receiver said. It is not retried and not stored as a delivery.

Authentication
API token (admin)

Path parameters

  • webhook_id
    string required

    The webhook’s id (whk_…).

Query parameters

  • project
    string optional

    The project’s id or slug. Needed only with a credential that can see several projects (the root token). With an API token it is ignored unless it names another project, which is 403.

Request

Terminal
curl -X POST "https://api.sypnia.com/v1/webhooks/whk_4z6x8c2v0b1n/test" \
  -H "Authorization: Bearer $SYPNIA_ADMIN_TOKEN"

Response200

JSON
{
  "ok": true,
  "response_status": 200,
  "response_ms": 131,
  "error": null
}

Errors

  • 404not_found

    No webhook has this id in the project.

The errors every endpoint can answer (401, 403, 429, 500, 503) are on Errors, limits, pagination.

Sections

Start hereWhat Sypnia is, how it works, what is open source and what is the paid cloud, and the two ways to get your first problem in plain words.ConceptsThe ten ideas Sypnia is made of, each defined precisely, from a project and its keys to problems, traces and alerts.SDKsHow your app sends data to Sypnia. One SDK for the browser, one for Node, one for Next.js, and the OpenTelemetry intake for every other backend.The agentHow Sypnia analyses a problem, what it writes, what it sends to a model and what it never does.MCP and skillsConnect your coding agent to Sypnia so it can ask what is failing in production, read what it needs to fix it, and set Sypnia up for you.API referenceThe Sypnia HTTP API: one API for the open-source engine and for Sypnia Cloud, with every endpoint, parameter, response and error.CLI referenceThe sypnia command: how to install it, the variables it reads, what its exit codes mean, and where each command is documented.Self-hostingWhat you run when you host the Sypnia engine yourself, what you need, what it costs, and what you do not get compared with Sypnia Cloud.How the engine is builtThe whole Sypnia engine on one page, from a click in your app to the sentence your coding agent reads, with the design rules and the code that holds them.Sypnia CloudHow the paid service works, from organizations and roles to plans, limits, billing, where your data lives, the GitHub App and support.Privacy and securityWhat Sypnia collects from your app and its users, what it never collects, how masking works, how to delete data, and how the service is protected.LicensingWhich licence covers each part of Sypnia, what you may do with it, how the name may be used, and the terms of a contribution.GuidesStep-by-step recipes for the common ways to use Sypnia, from apps made with AI builders and Next.js on Vercel to Supabase, source maps in CI, alert e-mails from your own engine, and moving from Sentry.ReferenceThe pages you look things up in, from the event schema and the glossary to what is planned, the changelog and the common questions.
↑↓ to move↵ to openEsc to close