Connect GitHub.
Everything else is handled.
Jetpacked is not a blank server you point at a repo. It reads your codebase, understands what it needs, and prepares every piece before your app starts.
Six phases.
Zero decisions for you.
Every deploy goes through a defined sequence: clone, detect, build, provision, migrate, and start. Each phase streams live logs to your dashboard so you always know what's happening. No black-box surprises.
If a step fails, Jetpacked surfaces the exact error with the relevant log lines, not a generic "deployment failed" message.
Clone
Fetches your repo from GitHub at the selected branch and commit.
Detect
Rule-based engine reads config files, and directory structure to identify your framework, runtime, ORM, and services.
Build
Runs the install and build commands appropriate to your stack. No Dockerfile required.
Provision
Creates required services, generates secure credentials, and wires them into your environment.
Migrate
Runs your migration command automatically: Prisma, Drizzle, TypeORM, or a custom script.
Start
Launches your container with environment fully wired and HTTPS active.
What gets detected
automatically.
Jetpacked's detection engine reads your manifest files, config files, directory structure, and import patterns to determine the exact framework, runtime, and services your app requires, without asking you to fill in forms.
When the engine encounters something ambiguous, it resolves it using structured inference rules. Your full codebase is never sent to an AI model.
Laravel, Django, Rails coming soon
We handle the infrastructure.
You own the configuration.
Jetpacked automates as much as possible, but some things are specific to your app and your environment. Here's what you still set yourself, and why.
- Environment-specific secrets (API keys, OAuth credentials)
- Custom build commands when non-standard
- Worker process definitions
- Database storage tier
Smart wiring.
No hardcoded runtime values.
Apps often need values that only exist once deployed: service URLs, generated credentials, cache endpoints, callback URLs. Jetpacked lets you bind env vars to managed values, then resolves them at deploy time.
Real errors. Specific fixes.
Not "deployment failed." Jetpacked identifies the exact point of failure and tells you what to change, in plain language, with the log context that actually matters.
We detected a Prisma schema but no migration command. Add npx prisma migrate deploy to your deploy settings.
Your app is binding to localhost instead of 0.0.0.0. It won't accept external traffic. Set HOST=0.0.0.0 in your environment.
Build succeeded but no start command was found. We detected an Express app. Add a start script to your package.json.
Your build failed on the TypeScript compilation step. The last log lines show the exact file and line. Fix the error and redeploy.
Your app is listening on port 3001 but Jetpacked expects port 8080 for this stack. Set PORT=8080 or update your app's port config.
See exactly what's happening.
No SSH. No server dashboard. Every log line from your deployment and running container is accessible directly from your Jetpacked project dashboard.
Deployment logs
Every step of your clone, install, build, and database setup is logged and accessible from your project dashboard.
Runtime logs
stdout and stderr from your running container, always accessible without SSH or a server dashboard.
Log retention
7 days of log retention.
Crash detection
Jetpacked shows a clear error state when your container exits unexpectedly, with the last log lines visible.
Your domain.
HTTPS in 60 seconds.
Every project gets a Jetpacked subdomain instantly. Connect your own domain on plans that include custom domains, and Jetpacked handles the SSL certificate automatically.
- 1
Add your custom domain in project settings.
- 2
Point your DNS CNAME to the Jetpacked-provided hostname.
- 3
Jetpacked provisions TLS automatically, usually within 60 seconds.
- 4
Your app is live at yourdomain.com with a valid certificate.
Custom domains available on Starter, Pro, Power.
Queues and crons.
No extra infra.
Run background workers, queue consumers, and scheduled jobs alongside your web process, all inside the same project. No separate services to provision, no external queue brokers to configure.
- Declare workers in your project settings
- Workers restart automatically on every deploy
- Included on Starter, Pro, Power
Ready to stop configuring
and start shipping?
Connect your GitHub repo and let Jetpacked handle the rest. Free plan, no credit card.