Support
How to get help with Sypnia on each plan, what to send so we can help fast, and what we do not promise.
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 are | Support | Where |
|---|---|---|
| Self-hosting the engine | Community | The engine’s repository on GitHub: questions, bug reports and ideas. The repository opens at launch. |
| On the Free plan | Community | The same place. |
| On the Builder plan | Write to support@sypnia.com. A person answers. | |
| On the Team plan | Priority e-mail | The 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:
- Which project, and which environment.
- What you expected and what happened. One sentence each.
- When, with the time zone.
- A link to the problem, the session or the page in the app, if it is about something you see there.
- For an SDK question: the package and its version, your framework, and the snippet where you start the SDK.
- 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.