How it works
Five steps to a live application
You need a GitHub account, an invitation, and a Next.js repository.
Accept your invitation
Invitations are tied to a GitHub username. Open the link, then sign in with that GitHub account. KaribaCore does not store a separate password.
Connect GitHub
Install the KaribaCore GitHub App and choose which repositories it can read. Signing in identifies you; the app is what gives a workspace access to code.
Import a repository
Pick the repository and its production branch. Add any environment variables the application needs before the first build.
Deploy
KaribaCore installs dependencies, builds the application, and starts it. Once it passes its health check it becomes the production release at your project address.
Keep shipping
Each push to the production branch builds and releases. Add a custom domain, turn on pull request previews, and roll back if a release misbehaves.
What your repository needs
- A Next.js application with a build script.
- One committed lockfile:
package-lock.jsonfor npm orpnpm-lock.yamlfor pnpm 10. - One application at the repository root. Multi-package workspaces are not supported yet.
Supported pilot workload
Check compatibility before deploying. Supported: Next.js 15 and 16 · React 18 and 19 · Node 22 or 24, and Vite 6, 7 and 8 single-page apps (React, Vue, Svelte and others). Node is chosen from engines.node in package.json (Node 22 when unset).
- Commit package-lock.json (v2 or v3) for npm, or pnpm-lock.yaml (v9) for pnpm 10, plus a build script. One app at the repository root; monorepos, Yarn and Bun are not supported yet. For Next.js, output: 'standalone' is optional and gives smaller images. For Vite, keep the default dist output folder.
- Build ceiling: 2 CPU, 3 GiB memory and 25 minutes for the whole job. App runtime ceiling: 1 CPU and 512 MiB memory.
- Default workspace allowance: 1 concurrent build, 4 runtime slots and 5 GiB of deployment images. Previews and release transitions use slots. Check Usage & plan for your actual allowance.
- Files are temporary. The bounded /tmp and application cache volumes are 64 MiB each. No durable uploads, local databases or managed databases are included.
- Outbound connections to public addresses are allowed on HTTP/HTTPS (80, 443), PostgreSQL (5432, 6543), MySQL (3306), Redis (6379), MongoDB (27017) and SMTP submission (465, 587). Private networks and SMTP port 25 are blocked.
- Active releases and the latest three activated versions are protected; other images may be removed after seven days. Build logs last 30 days, captured runtime logs seven days.
Full list of what KaribaCore runs, limits and fixes for common build errors
The starter includes a public HTTPS data demo and an optional Upstash Redis REST example. It explains repository setup and keeping service tokens in runtime variables.
Two workspaces created or owned per account. Contact [email protected] for an increase.
KaribaCore is invitation-only for now
Tell us what you would like to deploy and we will be in touch when a place is available.