Everything handled.
Nothing to configure.
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.
We read the repo.
You don't lift a finger.
Jetpacked's detection engine reads your package.json, 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 — never by sending your full codebase to an AI model.
Clone
Fetches your repo from GitHub at the selected branch.
Detect
Rule-based engine reads package.json, config files, and directory structure.
Build
Runs install and build commands appropriate to your stack.
Provision
Creates your database, generates credentials, injects the connection string.
Migrate
Runs your migration command — Prisma, Drizzle, or a custom script.
Start
Launches your app container with environment wired and HTTPS active.
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 and why — no black-box surprises.
If a step fails, Jetpacked surfaces the exact error with the relevant log lines — not a generic "deployment failed" message.
Smart wiring.
No hardcoded runtime values.
Apps often need values that only exist once they are deployed: service URLs, generated credentials, cache endpoints, callback URLs, and the final public app URL. Jetpacked lets you bind env vars to managed values, then resolves them during deployment.
At deploy time, placeholders become concrete values for the app, selected services, and generated credentials.
Database ready.
Connection wired.
When Jetpacked detects that your project needs a database, it provisions one, generates secure credentials, and injects the connection string into your environment — all before your app starts. Migrations run automatically as part of every deploy.
- Postgres, MySQL, MongoDB, Redis — detected from your dependencies
- Secure auto-generated credentials, no copy-pasting
- Migration commands run automatically on every deploy
- Storage from 512 MB to 50 GB
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 — accessible from your project dashboard.
Runtime logs
stdout and stderr from your running container, always accessible without SSH or a server dashboard.
Log retention
1-30 days of log retention depending on slot tier.
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.
You get a Jetpacked subdomain, can connect your own domain, and Jetpacked handles the SSL certificate.
- 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 on your own.
- Declare workers in your project settings
- Workers restart automatically on 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.