Docs

Support

How to get help with Sypnia on each plan, what to send so we can help fast, and what we do not promise.

Applies to EngineCloud At launch

View as Markdown
On this page
  1. Where to ask
  2. What we do not promise
  3. What to send
  4. What we look at to help you
  5. Before you write
  6. Reporting a security problem

This page is for anyone who is stuck. It covers Sypnia Cloud on every plan, and says where people who self-host the engine get help.

Where to ask

You areSupportWhere
Self-hosting the engineCommunityThe engine’s repository on GitHub: questions, bug reports and ideas. The repository opens at launch.
On the Free planCommunityThe same place.
On the Builder planE-mailWrite to support@sypnia.com. A person answers.
On the Team planPriority e-mailThe same address. Your messages are answered before the others.

Community support means the people who build and use Sypnia help each other in the open. We read it and answer when we can. It is the right place for anything about the open-source engine, on any plan, because the answer then helps the next person.

Billing questions and anything about your account are answered by e-mail on every plan, including Free.

We answer in English and in Spanish.

What we do not promise

Sypnia is run by a small team, and these docs only promise what is true.

  • No guaranteed response time on any plan at launch. «Priority» means first in line, not a number of hours.
  • No phone or chat support.
  • No service level agreement with credits for downtime.
  • No public status page at launch. If Sypnia Cloud has an incident that affects your data or your alerts, we tell the owners of the affected organizations by e-mail.

What to send

A message with these gets an answer without a round of questions:

  1. Which project, and which environment.
  2. What you expected and what happened. One sentence each.
  3. When, with the time zone.
  4. A link to the problem, the session or the page in the app, if it is about something you see there.
  5. For an SDK question: the package and its version, your framework, and the snippet where you start the SDK.
  6. For an API or MCP question: the request you made and the request id from the answer.

Do not send secrets. Never paste an API token (sps_…) or your self-hosted root token in a message or a public report. An ingest key (spk_…) is public and fine to share. If a token was exposed, revoke it first, then write.

What we look at to help you

To answer, we may need to look at your project in Sypnia Cloud: the problem or the session you point at, the project’s settings, the usage counters. We look at what the question needs and no more. The rules for staff access are in Security practices.

We cannot see a self-hosted engine. For those, we can only work with what you send.

Before you write

Many answers are already here:

  • Nothing arrives: Troubleshooting.
  • A number looks wrong: the Concepts pages define how each one is counted.
  • A limit was reached: Plans and limits.
  • Something you expected is missing: Planned lists what is not available at launch.
  • Common questions: the FAQ.

Reporting a security problem

If you found a way to read or change data that is not yours, do not post it in public. Write to support@sypnia.com with «Security» in the subject. What to include, and what we do with a report, is in Security practices.

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