KaribaCore
Request access

How it works

Five steps to a live application

You need a GitHub account, an invitation, and a Next.js repository.

Supported pilot workload

Check compatibility before deploying. Supported: Next.js 15 and 16 · React 18 and 19 · Node 22 or 24. Node is chosen from engines.node in package.json (Node 22 when unset).

  • Commit package-lock.json (lockfile v2 or v3) and a build script. One app with npm; npm workspaces, pnpm, Yarn and Bun are not supported yet. output: 'standalone' is optional and gives smaller images.
  • 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.

Download the tested starter

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.

  1. 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.

  2. 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.

  3. Import a repository

    Pick the repository and its production branch. Add any environment variables the application needs before the first build.

  4. 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.

  5. 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.
  • A package-lock.json created by npm, committed to the repository.
  • One application per repository. npm workspaces are not supported yet.

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.

Request accessSign in