# Open source and Sypnia Cloud

> Exactly what is free and open, what is the paid service, what they share, and how to choose between them.

Applies to: the Sypnia engine (open source, self-hosted) and Sypnia Cloud (paid service). Status: at launch.  
Source: https://docs.sypnia.com/start/open-source-and-cloud/

For agents: Read this to know whether a feature exists in the open-source engine, in Sypnia Cloud, or in both, before you tell someone how to use it.

This page is for anyone deciding how to run Sypnia. It applies to both ways, because it is the page that tells them apart. Every other page of these docs carries a badge that says which one it is about: **\[Engine]** for the open-source engine, **\[Cloud]** for the paid service.

> **In plain words**
>
> The engine is the part that does the work: it receives what your app reports, stores it and finds the problems. It is open source and free. Sypnia Cloud is that same engine, run by us, with what a service needs around it: accounts, the full app, e-mail, pull requests. You pay for the second so that you do not have to run the first.

## The two, side by side

|                         | Sypnia engine (open source, self-hosted)                                                                                                                                             | Sypnia Cloud (paid service, with a free tier)                                      |
| ----------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------- |
| Receive, store, analyse | Ingest, storage, aggregation, problem grouping, sessions, replay data and uptime checks.                                                                                             | The same engine, run by us.                                                        |
| Read it                 | The HTTP API, the MCP server, the CLI and the **Console**: one built-in page with the problems list and the session replay viewer.                                                   | The full app: replay player, performance, uptime, daily summary, search and teams. |
| Who gets in             | Projects, ingest keys and API tokens. No users, no organizations.                                                                                                                    | Users, organizations, roles, plans and billing.                                    |
| AI                      | The plain-language analysis and the ready prompt, with **your own model key**: OpenRouter, or any OpenAI-compatible endpoint. Off until you set a key.                               | Included, no key needed. **Pull requests** opened by the Sypnia GitHub App.        |
| Alerts                  | Recorded, and exposed by the API, MCP, the Console and an outgoing webhook. **No e-mail sender** in the default deployment: delivery is yours to connect, and the docs give recipes. | **E-mail and in-app alerts**, and the daily summary by e-mail.                     |
| Cost                    | Free. No limits set by us. You pay for your own infrastructure.                                                                                                                      | Free, Builder USD 10 a month, Team USD 49 a month.                                 |
| Support                 | Community.                                                                                                                                                                           | Community on Free, e-mail on Builder, priority e-mail on Team.                     |

Prices are a proposal until they are confirmed. [Plans and limits](https://docs.sypnia.com/cloud/plans-and-limits) has the limits of each plan.

## The same engine

Sypnia Cloud is not a different product. It is our deployment of the same engine, plus a private control plane: accounts, billing, the app and the GitHub App. Three things follow from that.

- **Your app sends the same events.** The SDKs, the event format and the OpenTelemetry intake are the same. Only the address changes.
- **You read the same data the same way.** The HTTP API has the same paths, and the MCP server has the same tools. A script or a coding agent that works against one works against the other.
- **Nothing in the analysis is held back.** Problem grouping, sessions, replay data, traces, performance and uptime checks all live in the engine. The agent's analysis is in the engine too, and runs once you give it a model key.

The addresses are the only names that differ:

|                             | Sypnia Cloud        | Your own engine                                     |
| --------------------------- | ------------------- | --------------------------------------------------- |
| Where your app sends events | `ingest.sypnia.com` | Your base URL, same paths                           |
| The HTTP API                | `api.sypnia.com/v1` | Your base URL, same paths                           |
| The MCP server              | `mcp.sypnia.com`    | The `@sypnia/mcp` package, pointed at your base URL |
| Where a person reads it     | `app.sypnia.com`    | The Console, served by your engine                  |

## What is in the open-source engine **\[Engine]**

Everything needed to receive, store, analyse and read your data, with no limit set by us.

- **Receive, store, analyse.** Ingest, storage, aggregation, problem grouping, sessions, replay data and uptime checks.
- **Read it.** The HTTP API, the MCP server, the CLI, and the Console: one built-in page with the problems list and the session replay viewer.
- **Who gets in.** Projects, ingest keys (`spk_…`) and API tokens (`sps_…`), created with the root token you set when you install. There are no users and no organizations.
- **The agent.** The plain-language analysis and the ready prompt, with your own model key. It is off until you set one.
- **Alerts.** Every alert is recorded, and you can read it through the API, MCP and the Console. The engine sends it to a webhook if you set one. The default deployment has no e-mail sender.

The engine is one program, `sypnia`. It needs an S3-compatible bucket and one Postgres database, and nothing else.

## What Sypnia Cloud adds **\[Cloud]**

The things a hosted service needs, and the ones that only make sense when someone runs them for you.

- **The full app.** The replay player, performance, uptime, the daily summary, search and teams.
- **Accounts.** Users, organizations, roles, plans and billing.
- **The agent, included.** No model key to get or to pay for separately.
- **Pull requests.** The Sypnia GitHub App reads your repository, writes a branch named `sypnia/<problem>`, and opens a pull request with the change and a test. A person reviews it and merges it. Sypnia never merges code.
- **Alerts that reach you.** By e-mail and inside the app, plus the daily summary by e-mail.
- **Support by e-mail.** Priority e-mail on the Team plan.

> **Note: Pull requests without Sypnia Cloud**
>
> The engine does not open pull requests. It gives your own coding agent what it needs to write the fix: the ready prompt, and the MCP server, which lets Cursor, Claude Code or another agent read the problem, its trace and its replay.

## What you choose when you self-host

The default deployment of the engine contains only what cannot be left out. Every piece that depends on a provider is a choice. These docs explain the common options for each one, and say what Sypnia Cloud uses.

| Piece          | Default deployment                                                   | Alternatives the docs explain                                                                                     | Sypnia Cloud uses                                     |
| -------------- | -------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------- |
| Object storage | The bucket the template creates.                                     | Any S3-compatible store: Amazon S3, Cloudflare R2, MinIO.                                                         | Amazon S3.                                            |
| Database       | A Postgres URL you provide, or the one the template creates.         | Amazon RDS, Supabase, Neon, or your own server.                                                                   | Postgres.                                             |
| Alert delivery | **None.** Alerts are recorded, and sent to a webhook if you set one. | Recipes: e-mail with Amazon SES, e-mail with any SMTP server, or your own function on the webhook.                | E-mail through Amazon SES, and alerts inside the app. |
| AI provider    | **Off** until you set a key.                                         | OpenRouter, the OpenAI API, the Anthropic API, Google Gemini, or any OpenAI-compatible endpoint, hosted or local. | OpenRouter.                                           |
| Pull requests  | Not in the engine.                                                   | Use the prompt or the MCP server with your own coding agent.                                                      | The Sypnia GitHub App.                                |

Alert delivery is the choice most people meet first, because the default is to deliver nothing:

**A piece you choose: Alert delivery.** Gets an alert from the engine to a person.

- **Default deployment:** **None.** Alerts are recorded, and sent to a webhook if you set one.
- **Sypnia Cloud uses:** E-mail through Amazon SES, and alerts inside the app.

Sypnia has no WhatsApp and no Slack integration, in the engine or in the Cloud.

## What each one costs

**The engine is free.** There is no licence fee and no limit set by us on projects, events, replays or how long you keep data. You pay your own provider for the bucket, the database and the compute. As a reference, the deployment Sypnia was extracted from, one product in production, costs about USD 15 to 25 a month in infrastructure. [Scaling and cost](https://docs.sypnia.com/self-hosting/scaling-and-cost) explains what makes that number move.

**Sypnia Cloud has a free tier and paid plans.** You pay for how much you send, not for features: every plan has replay, traces, the agent, the prompt and the MCP server. The plans differ in projects, events, replays, how long data is kept, people on the account and pull requests a month.

## Which one to use

Use **Sypnia Cloud** if you want to see your first problem today and you do not want to run anything. This is the right choice for most people who build with Lovable, Bolt, v0, Replit, Cursor or Claude Code.

Use **the engine** if your data has to stay on your own infrastructure, if you want no limit other than your own servers, or if you want to read and change the code that analyses your app. Expect to run a database and a bucket, to keep the engine upgraded, and to connect alert delivery and a model key yourself.

You can start on one and change to the other. Your app's code stays the same: you change the address and the ingest key in the SDK. Sypnia does not copy your history from one to the other.

## Next
