Core concepts
Workspaces, projects, services, deployments, and how they fit together on Bytstack.
Workspaces
A workspace is your team boundary: members, billing, and GitHub connections. Switch workspaces from the dashboard header. Roles control who can deploy, manage billing, or read-only view resources.
Projects
A project groups related services and (optionally) managed databases. Shared project env vars can be inherited by services. Most teams map one GitHub repo (or monorepo) to one project.
Services
A service is a deployable unit with a type:
| Type | Use for | Public URL |
|---|---|---|
| Web | APIs, SSR (Next.js, Remix), Node servers | Yes |
| Static | SPAs (Vite, CRA, etc.) | Yes |
| Worker | Background jobs, queue consumers | No |
| Cron | Scheduled tasks | No |
Rule of thumb: client-side SPA with npm run build → Static. Long-running Node HTTP process → Web.
Deployments
Each deploy is an immutable attempt: clone → build → publish → release. You can roll back to a previous live version without rebuilding. Preview deployments can be created for pull requests.
Domains & edge
Services get a platform hostname by default. Custom domains attach with DNS verification and automatic TLS. Traffic swaps to new web deployments with zero downtime.
Data
Managed PostgreSQL attaches on a private network. Connection strings are injected as env vars; external TLS access is optional and allowlisted.
Hierarchy
Workspace → Project → Services + Databases. Members and billing hang off the workspace; domains and shared env hang off the project.