Guides
Step-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.
A guide takes one real situation from start to finish: what you will have at the end, numbered steps with the exact code, and what you should see after each one. The SDK pages are the reference; the guides are the routes through them.
Every guide says whether it applies to the open-source engine Engine, to Sypnia Cloud Cloud, or to both. The SDKs are the same for both, so most guides differ in one line: the address the SDK sends to.
-
Apps built with Lovable, Bolt, v0 or Replit
The prompt to give your builder, and how to check that it did it right. No code reading needed. - Variables, preview deployments, source maps at build and functions.
- Database calls from the browser, Edge Functions, and people from Supabase Auth.
- Upload source maps and register each release from GitHub Actions.
-
Alert e-mails from a self-hosted engine
The engine sends no e-mail by default. Add it with Amazon SES or any SMTP account. - What maps to what, what to remove, and what has no equivalent yet.
Which guide for which situation
| You | Start with |
|---|---|
| Built your app by describing it to an AI builder | Lovable, Bolt, v0 or Replit |
| Deploy a Next.js app on Vercel | Next.js on Vercel |
| Use Supabase as your backend | Supabase apps |
See checkout-3f9c.js:1:48211 in a stack instead of your own file | Source maps in CI |
| Run your own engine and want an e-mail when something breaks | Alert e-mails from a self-hosted engine |
| Already use Sentry | Coming from Sentry |
| Have not installed Sypnia yet | A quickstart: Sypnia Cloud or self-host |