Getting Started
Getting Started
The first Deploir path is deliberately operational: get access, connect a repository, review detected runtime and configuration, set environment variables, confirm domains, deploy, and verify health.
1. Create or access your account
Use the marketing account-entry route to create a Base account or sign in. The account step exists to establish a real workspace before repository, domain, and release state are introduced.
- Create a Base account from the Start deploying path.
- Return through Sign in if you already have a workspace.
- Use the same workspace to keep projects, domains, support, and usage in one place.
2. Connect a repository
Base connects to GitHub after the workspace exists. The next action is repository selection, not an infrastructure panel.
Typical application fit
Primary branch: main
Detected runtime: Next.js 15 / Node.js 20
Package manager: npm or pnpm
Health endpoint: /api/health
Domain review: optional before first deploy3. Review the detected runtime
Deploir surfaces the detected framework, package manager, build path, start expectations, output directory, and likely blockers. The goal is to confirm what the product actually sees before any deployment action is promoted as ready.
| Review item | What to confirm |
|---|---|
| Framework | Next.js, static site, Node API, or Docker fit |
| Branch | The correct deployment branch is selected |
| Build path | Install, build, and runtime expectations are accurate |
| Health check | A customer-safe health endpoint or route exists |
4. Configure environment and domains
Environment variables, routing, and domains are part of the same launch path. Sensitive values stay out of public forms and are handled inside the protected product boundary.
Sensitive values
Do not send secrets or provider credentials through the public contact path. Configure them only inside the protected Base workspace.
5. Deploy and confirm health
A launch is only complete when the deployment, route, TLS state, and health response are visible together. The recovery path should remain legible next to the active release.