Supabase but for non-db shit.
Supabase does God's work for developers: it took Postgres, the hardest part of every stack to run well, and turned it into something you get by signing up. coss.com does the same for everything that sits above the database. Email, SMS, video, scheduling: one API key, one SDK, one bill.
What Supabase did for the data layer
Before Supabase, a new product started with a week of plumbing: a database to host, back up and upgrade, auth to bolt on, files to put somewhere, a way to push changes to the browser. Supabase folded all of that into a project URL and an API key, kept Postgres at the centre, and open-sourced the lot. The data layer became a solved problem.
We're fans. coss.com itself runs on Postgres, and we have no plans to host yours. Keep your database where it is: Supabase, Neon, RDS, a box under your desk.
What's left once the database is solved
A working product still has to reach people. It sends a receipt, texts a verification code, puts two users on a call, books a meeting. Each of those has been a separate vendor: its own account, key, dashboard, webhook format, retry rules, rate limits, invoice and compliance paperwork. Four vendors to ship one product, and four places to look when something doesn't arrive.
That is the application layer, and it is what coss.com is for. Not the data under your app, but everything your app does with it.
One vendor for the application layer
Every coss.com product is built the same way: one key, one SDK namespace, the same webhooks, logs, rate limits, idempotency and API versioning. Learn one and you know them all.
- Email
coss.emailTransactional email from your own domains, tracked to every recipient. - SMS
coss.smsText messages worldwide, on the same key, events and logs as email. - Video
coss.videoRooms and recordings for the calls inside your product. - Scheduling
coss.schedulingAvailability and bookings, from the team behind Cal.com. - Hooks
coss.hooksWebhooks as a service: send a message once, coss.com delivers it to every endpoint your customers registered. - Risk
coss.riskWhether a sign-up, login or other event looks like abuse, and why, with rate limiting for your own endpoints.
Behind the products sit the pieces every one of them needs: verified domains, receiving, suppressions, DMARC and reputation, delivery logs and drains, signed webhooks, audit log, metered billing. Those are built once and shared, not reinvented per product.
Open source, built for agents
The platform is open source under the AGPL, with an MIT SDK, MCP server and CLI, so what you build on stays inspectable and yours to run. The docs are written so a coding agent can wire a product in from one prompt, and so can you.
coss.com is built by the team behind Cal.com. Shipyard and kloq come from the same shop.