snoozestack

Runs local. Ships global

Build the app. We'll run the cloud.

Your whole backend is one portable runtime your coding agent can drive. Run the entire cloud on your machine, then publish the same thing to managed production servers with one command.

Request early accessSee the anatomy →
claude code — golf-app

Local development

Software development without the infrastructure detour.

One command runs the whole backend on your machine — and serves the same console you get in production, so you can see your data, functions, and users while you build them.

Projects/Golf App◒

Golf App

golf-app · created 2026-01-15 04:00

Connect your project
Quick start
01
Install and log in to the CLI
snoozestack user loginInstall guide →
02
Link your project folder
snoozestack link --project golf-appCLI guide →
03
Make the MCP connection
Set up MCP →
API endpointProduction
SNOOZESTACK_URL
https://golf-app.snoozestack.com
Project API keys
SNOOZESTACK_ANON_KEY (public)
••••••••••••••••••••
SNOOZESTACK_SERVICE_ROLE_KEY (secret — server-side only)
••••••••••••••••••••
JWT secret
••••••••••

Complete from the first run

Functions, data, auth, storage, jobs, push, and Signals are one runtime, designed to work together.

The whole cloud, locally

Run your application infrastructure on your machine with one native service—no Docker setup.

Production in one publish

Send the same project to Snoozestack and we run it on managed production infrastructure.

01 · The base — data & storage

State the runtime owns.

A database built from your committed schema, a directory per declared bucket, and the signals store — all under one directory you can mount, replicate, or throw away.

Built for agents

Your agent's whole cloud.

The project is files and every operation is a structured command — so an agent doesn't stop at code. It stands the backend up, publishes it, and reads back what happened.

Connect your agent →
my-appcloud running locally
Application infrastructure
◆snoozestack/project.tomlproject
└snoozestack/migrations/001_init.sqldata
└snoozestack/functions/create-note.tsfunction
└snoozestack/push/note-ready.tomlpush
$ snoozestack dev
✓ local cloud ready at localhost:4123
functions · data · storage · signals
Production
$ snoozestack publish
packing current project…
validating capabilities…
✓ version 01K3 published
live01K3
https://my-app.snoozestack.app

Managed hosting

One publish, and it's ours to run.

snoozestack publish takes the project you just ran and puts it live as an immutable version — on managed hosts, behind your own domain, replicated and watched. What it's doing out there comes back as Signals.

How publishing works →

Signals

Everything this project emits, newest first — events from your app and logs from its functions, in one stream.

Filter by message text…
24H7D30D90D
23 Aug 06:00:0029 Aug 18:45:00
DateSignalEvent message
29 Aug 18:44:51eventSigned Up {"source":"shared link"}
29 Aug 18:40:15eventLogged a Round {"strokes":86,"course":"Corica"}
29 Aug 18:38:44log[book-tee-time] 201 in 22ms {"namespace":"default"}
29 Aug 18:31:09eventCame Back {"days_since_signup":4}
29 Aug 18:27:53eventLogged a Round {"strokes":92,"course":"Lincoln"}
29 Aug 18:19:31log[post-round] 201 in 41ms {"namespace":"default"}
29 Aug 18:12:07eventSigned Up {"source":"shared link"}

Your app deserves its own cloud. Not a cloud project.

Build the product locally. Publish the infrastructure with it. Let Snoozestack keep it running.

Request early access →