Docs

Planned

The honest list of what Sypnia does not do at launch, in three groups: what is planned, what is absent with no promise, and what Sypnia will not do by design. No dates.

Applies to EngineCloud At launch

View as Markdown
On this page
  1. Planned
  2. SDKs and platforms
  3. Kinds of data
  4. Access and identity
  5. Not in the first version
  6. Not planned, by design
  7. Ask for something
  8. For coding agents

This page is for anyone who expected something and did not find it, and for coding agents, so that they never describe a planned thing as if it existed. It covers the open-source engine Engine and Sypnia Cloud Cloud.

Everything else in these docs describes what exists at launch. This page is the one place for what does not. It has no dates, on purpose: a date we miss would be a promise we broke.

GroupWhat it means
PlannedWe intend to build it. In the docs it carries the Planned badge. It is not started, or not finished.
Not in the first versionIt does not exist at launch, and we make no promise either way.
Not planned, by designA decision. Do not wait for it.

When something ships, it leaves this page and appears in the changelog.

Planned

SDKs and platforms

PlannedWhat to use until thenDescribed in
Native iOS and Android SDKsMobile apps built as web views (Capacitor, Cordova, a wrapped web app) work at launch with the browser SDK. A fully native app has no SDK.Browser SDK
SDKs for Python, PHP, Go and RustSend traces from any backend with OpenTelemetry, over OTLP/HTTP.OpenTelemetry
An adapter for AWS Lambda handlers that receive API Gateway or function URL events, in @sypnia/nodeThe OpenTelemetry intake. Fetch-style functions are covered at launch by wrapFetchHandler.Node SDK
Bun, Deno and Cloudflare Workers as tested runtimes for @sypnia/nodewrapFetchHandler uses only web-standard APIs, so it may work. It is not tested there.Node SDK
More database drivers traced by themselves in @sypnia/node: MySQL, MongoDB, Redis, Prisma’s own engineWrap the call in span(), or use the driver’s OpenTelemetry instrumentation. pg and Supabase calls are traced at launch.Node SDK
The Edge runtime in Next.js: routes with runtime = 'edge', and middlewareNothing. That code is not traced and its errors are not reported.Next.js SDK
Source maps for Next.js server bundlesA server error’s stack shows the built file. Its route, its trace and the page that showed it are there.Next.js SDK
Sampling of successful server requestsEvery request is traced. Leave routes out with ignoreRoutes.Sampling and quotas

Kinds of data

PlannedWhat to use until thenDescribed in
LogsSypnia does not collect logs. OTLP logs are refused with 404.OTLP
Custom metrics and dashboardsCustom events with track(name, props) from the browser, counted per day. For your own charts, read the API or the daily Parquet files of a self-hosted engine.What Sypnia is

Access and identity

PlannedWhat to use until thenDescribed in
Single sign-on (SSO) CloudSign in with e-mail and password, or with GitHub.Organizations and teams
A signed identity for sending, for apps that need proof of who is sending eventsThe public ingest key is the only credential for sending. Allowed origins, rate limits and quotas protect it.Projects, keys and tokens

Not in the first version

These do not exist at launch. They are listed so that you do not look for them, not because they are promised.

Not at launchWhat there is instead
Custom events from the server. track() exists in the browser SDK only.Send the event from the browser, or wrap the step in span() with attributes.
A warning before a certificate expires, in uptime checks.An expired certificate fails the check, and the «App down» alert says why.
A public status page for your app, fed by uptime checks.GET /v1/uptime/checks has the data to build one.
A public status page for Sypnia Cloud, a guaranteed response time, a service level agreement. CloudOwners of affected organizations are told by e-mail. See Support.
Signing in to the MCP server through the browser (OAuth).An API token in the client’s configuration. See MCP authentication.
Identifying people from OpenTelemetry attributes.A trace takes the person of its session. See Identifying people.
Tags, contexts and extra data on an error, and searches or saved views over them.An error carries its session, person, account, release, route and trace. See Coming from Sentry.
One session across several origins, such as shop.example and app.shop.example.Each origin has its own sessions.
Sub-teams, or access per project inside an organization. CloudEvery member sees every project. Use two organizations.
Two-step sign-in of Sypnia Cloud’s own. CloudSign in with GitHub and use GitHub’s.
A choice of region, and encryption keys that you manage. CloudEverything is in us-east-1. To keep data elsewhere, self-host.
A one-click export of a project. CloudEverything can be read through the API while it is kept.
A public API for users, organizations, plans and billing. CloudThe app.
Pull requests on GitHub Enterprise Server, GitLab or Bitbucket. CloudThe prompt, or the MCP server, with your own coding agent.
Deleting a single problem, or only a replay, through the API.Ignore the problem; delete the session to remove its replay. See Deleting data.
Retention per project on a self-hosted engine. EngineOne set of retention settings for the whole engine.
Uptime checks from several places on a self-hosted engine. EngineChecks run from where your worker runs. Sypnia Cloud checks from three regions.
More screens in the Console. EngineThe Console shows problems and replays. The rest is in the API, the CLI and the MCP server. See The Console.
A measured cost and capacity table for the engine. EngineEstimates with their arithmetic. See Scaling and cost.

Not planned, by design

These are decisions, not gaps.

Sypnia will notBecauseWhat there is instead
Send alerts to WhatsApp or Slack, in the engine or in Sypnia CloudAlerts are e-mail and in the app on Sypnia Cloud, and a webhook everywhere.The alert webhook, and your own function on it. See Alerts and webhooks.
Put an e-mail sender in the engine’s default deploymentThe default deployment holds only what cannot be left out.A recipe: Alert e-mails from a self-hosted engine.
Open pull requests from the enginePull requests need an app installed in your repository, which is part of Sypnia Cloud.The ready prompt and the MCP server, with your own coding agent.
Merge code, or push to your default branchA person reviews and merges.Pull requests.
Add users and organizations to the engineThe engine knows projects, keys and tokens. Accounts are Sypnia Cloud.One API token per person.
Record what a person types, or let it be unmaskedIt is the one thing that must never leave the browser.Masking.
Let the agent read replay recordingsThe analysis works from events, stacks and traces.Models and what is sent.
Promise a specific AI modelModels change. On Sypnia Cloud we choose and change them; on the engine you choose.Models and what is sent.
Require a service besides Postgres and a bucket to run the engineTwo stores are the design.How the engine is built.

Ask for something

  • For the open-source engine and the SDKs: open an issue in the repository and say what you need it for. See Contributing. Several things on the planned list are good places to help.
  • For Sypnia Cloud: write to support@sypnia.com.

Asking does not move a date, because there are none. It does tell us what to build first.

For coding agents

If you are an AI agent reading these docs: nothing on this page exists at launch. Do not write code that calls it, do not tell a person to configure it, and do not present it as available. Offer the alternative in the middle column instead.

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