The Cymbiote Platform is the delivery substrate our squads use on client engagements: an opinionated set of services for authentication, content, media and observability that removes the first six weeks of undifferentiated work from every project.
These guides document the parts clients own and operate after handover.
Who this is for
Engineers taking ownership of a system we built, or integrating with one. It assumes you are comfortable with HTTP APIs, a terminal and your own cloud console. It does not assume you have worked with us before.
How this is organised
- Getting started — accounts, authentication and your first successful request.
- Platform — the services themselves and how they fit together.
- Integration — webhooks, SDKs and the patterns partners use most.
- Operations — running it: monitoring, incidents, backups and upgrades.
Conventions
Anything in monospace is a literal value you type or receive. Placeholders appear in angle brackets, like <your-project-id>, and never include the brackets in real usage.
Getting help
Every client has a named engineer and a shared channel. For anything urgent, use the escalation path in your handover pack rather than email — it pages someone.