Skip to main content
Graviton is the architecture every Stardeck app runs on. Your app is a Next.js 16 App Router project that deploys as a Cloudflare Worker, talks to the platform through installed SDKs, and is carried forward by a versioned upgrade rail. These pages are for the person writing the code. If you are looking for how to use the product — agents, dashboards, publishing — start at the documentation home.

​
Start here

Constraints

What the runtime refuses, and which files the platform owns. Read this first.

Compared to plain Next.js

Same framework, different boundaries. What you do differently here.

The SDKs

The packages installed in every app, and where each one’s full API lives.

​
The shape of an app

Two things in that diagram are easy to miss, and they shape everything else:
  • Your code is not the first hop. Hostname classification, tenant lookup, signed-in user resolution and public/internal visibility are decided in the shared dispatch worker before your app runs.
  • Your app owns no infrastructure. There is no database you provision, no queue you run, no bucket you name. Capabilities arrive as SDKs, and the platform holds the credentials.

​
Working on an app

Your local checkout is not what the preview serves. The hosted sandbox builds from the project’s main branch on the platform, so your edits appear in the dashboard preview only after they are pushed.

​
Operations that are not code

Some things a Stardeck app depends on are configured through the platform rather than committed to the repository — database schema, permission keys, role grants, Module installs. You reach them from the dashboard, or from your editor once Claude Code is connected. The constraints page maps each one to the place you actually do it.