The surface your users meet.
Publish the whole project — backend and site together — as an immutable version behind your own domain, reach people through push, and read what happened back as Signals.
Publish the project, not a pipeline
One command validates the files, creates a version, and moves live to it atomically.
Typed clients for your app
JavaScript and Swift SDKs carry identity, functions, and Signals into your codebase.
One language for what happened
Product events, logs, metrics, and delivery outcomes share one envelope and one store.
App, running
local developmentPublish the whole project at once
One command validates the files, pushes every declared resource in order, and records the result as an immutable version — the site and the backend it calls going live together, behind your own domain.
- Live by default; a named preview when you want to look first
- Promotion reuses the exact version you tested, without rebuilding
- Pointing live at an older version is the rollback
$ snoozestack publish
ok Checking project my-app — 3 functions, 1 site
ok Planning schema 2 changes against production's schema
ok Uploading sites "www": 4 uploaded
ok Uploading runtime 11 files as rt_01K3AB — not live yet
ok Deploying release release r12 is production — runtime healthy
╭─ "my-app" is live — release r12 ─────────────╮
│ live https://my-app.snzzz.com/ │
│ api https://my-app.snzzz.com/api │
╰──────────────────────────────────────────────╯Reach people, then read what happened
The SDKs carry identity, function calls, and event tracking into your app; push reaches users who aren't looking at it. Everything the app reports — product events, function logs, metrics, delivery outcomes — lands in one queryable stream.
- JavaScript and Swift clients with the same session model
- Push without provider credentials on your machine
- One export API, so the dashboard you prefer can read it
import { createClient } from "snoozestack-js";
const snoozestack = createClient("/api", KEY);
await snoozestack.identity.signInWithPassword({ email, password });
const { data } = await snoozestack.functions.invoke("my-notes");
snoozestack.signals.track("note_opened");Built for apps people actually use
What you build with App.
A frontend and its backend, together
The site is served from the same host as the API it calls, so a relative path works in development, on the project URL, and on your own domain.
Telling users something happened
A booking confirmed, a render finished. One call from the function that already knows, delivered to every device that person registered.
Knowing whether it landed
Ship the feature, then compare event volume before and after — the sequence of what people did, not just the state they ended in.
The application you ran locally becomes an immutable production release with one publish.
Why SnoozeStack →