Deployment
Deploy Openfront Ecommerce with explicit migration, secret, provider, and rollback ownership.
Openfront Ecommerce needs a Node.js runtime and persistent PostgreSQL. S3-compatible storage, email, payment, shipping, AI and marketplace secrets depend on the features you enable.
The repository's npm run build currently generates the Keystone schema, deploys Prisma migrations, and runs the Next.js build. Do not let multiple build workers race to migrate production. Split migration ownership into one reviewed release job where your host permits it.
Required planning
- Pin and review the exact source revision.
- Generate the Keystone/Prisma schema and run static checks.
- Back up production and test every pending migration on a realistic disposable clone.
- Supply
DATABASE_URLand a randomSESSION_SECRETthrough the host's secret manager. - Supply only the provider/storage/email variables used by the deployment.
- Apply migrations once, deploy, then run anonymous, authenticated and wrong-owner checks.
- Verify checkout totals, inventory, provider signatures/replay, fulfillment, refund and failure recovery.
- Keep an application rollback and database forward-recovery plan.
Hosting buttons
The source repository and catalog may provide Railway, Vercel or other convenience templates. They can create infrastructure, but they cannot verify your migration history, database sizing, object storage, background work, provider webhooks, security headers, backups or compliance needs.
Openfront can run on a Node-capable host with PostgreSQL if those requirements are met. “Deploy succeeded” is not the same as “commerce workflow is safe.”
Before putting customer or payment data into the instance, verify authorization, credentials, webhooks, concurrency, migrations, backups, restoration, and rollback against the exact release.