Database
- Local PostgreSQL
- Schema migrations
- Typed SQL queries
Free, and public on GitHubOne backend.
One backend.
Every app trusts it.
The website, the desktop app, the admin panel, the mobile app, and the extension all talk to one API. A change on the server shows up as an error in the editor, not as a bug report from a customer.
Your APIliveapi.my-app.com
GET/organizations2006ms
POST/invitations20012ms
GET/settings/members2008ms
PUT/members/role2009ms
GET/auth/session2004ms
preconfigured for you
A finished backend. Users included.
01
Configured before you arrive
Routes, database, cache and Docker. One create run and it answers on localhost:3000.
02
Your users are built in
Sign-in, sessions, teams, roles and invitations are live endpoints on day one.
03
Every app already talks to it
Five clients, one typed SDK, generated straight from these routes.
A change on the server
is an error in the editor.
pnpm typecheck0 errors, 6 apps
Try to break it
Rename a column. Every layer notices.
One name, declared in the database and inherited by every layer up to the button a customer clicks. Press the button.
one field, five layers
organization.seat_limit
start: the database
Postgres
the column
seat_limit integerPrisma
the schema
seat_limit IntKysely
the query
.select("seatLimit")Hono
the API route
c.json({ seatLimit })React
the UI
{data.seatLimit}
what this buys youpnpm typecheck: 0 errors
Every broken screen, listed
The compiler names each query, route and component that needs the change.
Refactors stop being scary
Follow the errors to done. Empty list, finished change.
AI agents fix their own mistakes
A wrong guess fails the typecheck in seconds, and the agent corrects it.
Six apps that cannot drift apart
Every app reads the backend's types. Nothing is left quietly behind.
5
Clients served by one backend
Website, desktop, admin, mobile, and extension, all reading the same typed API. One more app is one more client.
your api
web
admin
mobile
0
Hand-written API clients to maintain
Every route becomes a typed call on the frontend the moment it exists. No client to write, no client to let rot.
routes in, sdk out
nothing to keep in sync
1
Place every error is handled
Logged, shaped into a response, and reported to Sentry by one middleware. Nothing dies quietly.
loggedalwaysreportedsentryansweredtyped
What you get
What your business gets.
Nine outcomes, each with a receipt your developer can check. The whole repo is public.
One API, six apps
Web, desktop, admin, mobile and extension read the same SDK.
one SDK
Breaking changes get caught
Change the API and every dependent screen stops compiling.
Tested on every commit
Unit, integration and end-to-end suites gate every merge.
backend-e2e · CI
You hear about errors first
One middleware logs, shapes and reports every failure.
before support hears
Realtime built in
Live events ship with the same type safety as requests.
Live eventstyped like requestsPermissions, never a guess
Access rules check against a fixed list of actions.
Checkedat build timeBad days stay slow, not down
The cache fails soft; the API keeps answering from Postgres.
fails soft
Won't start half-configured
Every setting is validated at boot, with a clear message.
checked at boot
Your data, your database
Standard Postgres with migrations tracked in the repo.
Deploy with one command.
Everything goes live on your own host, with the URLs, secrets, and migrations already wired between the services. No dashboards, no YAML.
Fly.ioRailwayyour account, either way
Stack progress
00 / 4 services
- ApplicationDeploying
- Admin PanelQueued
- APIQueued
- MobileQueued
my-app.com
Production/Fly.io
Deploying
Being straight with you
What the backend does not include.
Better you read it here than find out on day two.
in the box
- sign-in and sessions
- organizations and roles
- invitations
- typed SDK
- realtime events
- error reporting
- cache
- migrations
not in the box
Billing, notifications, collaboration
Feature packs. Each adds its routes, schema and tests with one command.
Browse feature packsYour business logic
The plumbing is done. The thing that makes your product yours is yours to write.
Everything in the box
What the backend already handles.
The plumbing below is finished before you write a line. All of it is checkable in the public repo.
Realtime
- Live updates
- Authenticated WebSockets
- Collaboration-ready
Monorepo
- Shared packages
- Nx build orchestration
- Build only affected projects
Strict types
- Zod route validation
- Typed forms
- Strict TypeScript
Automatic SDK
- Generated from API routes
- Typed frontend client
- Catch breaking API changes
Deployment
- Web & desktop builds
- CI/CD configured
- Choose your host
'%20d='M23.262%202.652%2012.646%2022.787a.612.612%200%200%201-1.066.004L.768%202.656a.612.612%200%200%201%20.64-.906l10.262%201.834a.612.612%200%200%200%20.216%200L21.94%201.752a.612.612%200%200%201%20.643.9z'/%3e%3cpath%20fill='url(%23vite-b)'%20d='m17.284%203.74-7.875%201.543a.317.317%200%200%200-.254.295l-.485%208.181a.317.317%200%200%200%20.388.327l2.193-.506a.317.317%200%200%201%20.378.376l-.651%203.193a.317.317%200%200%200%20.397.367l1.355-.412a.317.317%200%200%201%20.397.368l-1.035%205.005c-.05.244.275.378.412.171l.091-.142%206.422-12.815a.317.317%200%200%200-.339-.46l-2.254.435a.317.317%200%200%201-.371-.402l1.471-5.099a.317.317%200%200%200-.34-.402z'/%3e%3c/svg%3e)
Source ownership
- Source in your repo
- Edit every feature
- No HypeStack runtime
Production tooling
- Sentry error tracking
- Structured logging
- Rate limits & caching
Feature packs to grow with
Every pack ships real source code: frontend, backend, and admin surfaces where the feature needs them. Add them when you need them, one command each.
FeatureProjectsOrg-scoped projects with members, favorites, icons, and a navbar switcher.Project CRUDMembers & rolesFeatureTeamsTeam workspaces with members, roles, icons, and email invitations on top of your starter.Team workspacesMember rolesFeatureWhiteboardA collaborative whiteboard: sticky notes, freehand ink, shapes, images, and layers on one infinite canvas, synced live.Infinite canvasLive multiplayerFeatureCalendarA working calendar: five views, drag to reschedule, event invites, and working hours.Five viewsDrag to reschedule
Two ways to install features
Same features underneath, different starting point. Either command resolves what the packs depend on, copies the source into your repository, and merges the database schema.
Ready-made
Take a template
A landing page, a design system, a themed layout, and the features already wired into it. Rebrand it, put your product in the middle, ship.
From scratch
$ hype-stack compose
✓ Auth✓ Billing✓ Teams✓ AI
Compose your own design
Your design and your choices, without rebuilding auth, billing, or notifications. Tick the packs you want and the CLI wires them into the open-source starter.
Questions, answered
Yes. Everything lands as plain source in your repository: frontend, backend, admin, database schema. There is no runtime dependency on us and nothing phones home.
Take the free one. Break it on purpose.
Clone it, rename a field, run the typecheck. If that does not convince your developer, nothing on this page will.
free / public / your repo