Hikari by CoreMVP
Getting started

Run locally

Start Hikari with local Supabase and reach your first signed-in Dashboard.

Start a fresh local application and create an account before configuring billing or hosting. This path does not migrate an existing Hikari deployment.

Before you start

Install Git, Bun 1.3.14, and Node.js satisfying >=20.19.0. Bun is pinned in package.json; choose a supported Node LTS release. Use a Bash-capable shell for ./coremvp.

Install Docker or a compatible runtime and start its daemon. Follow the vendors’ OS requirements and the local Supabase requirements. Check that the tools and running daemon are available:

git --version
bun --version
node --version
docker info --format '{{.ServerVersion}}'

Local signup needs no Stripe, hosted Supabase project or Vercel account. Add a Stripe test account and CLI for subscription testing, or your own hosted providers for deployment, when you reach those tasks.

Clone and install

git clone https://github.com/coremvp/hikari.git
cd hikari
bun install

Run the following commands from this repository root. Installation includes Supabase CLI 2.119.0 as a project-local dev dependency. Verify it before starting services:

bunx --no-install supabase --version
bunx --no-install supabase --help

No global Supabase install, supabase init, login or hosted project is needed.

Start local Supabase

bunx supabase start
bunx supabase migration up --local
./coremvp env sync

Supabase starts the hikari-oss project on ports 55420–55424. The template CLI writes the local connection settings to ignored .env.local, preserving existing Stripe settings. Keep this file private.

migration up --local applies the repository’s pending migrations, including the billing tables, to this local project before signup. If a migration reports existing legacy application data, stop and preserve it; this guide targets a fresh project. A database reset is unnecessary.

If Supabase cannot start, check that your Docker-compatible runtime is running and these ports are available. Run env sync only after Supabase is ready.

Open your application

bun run dev

Open localhost:3000 and select Create an account. Signup creates your Supabase account, signs you in, and opens Dashboard immediately. Open Account to see subscription controls. Billing remains unavailable until you configure Stripe.

If a required setting is missing, run ./coremvp env list. It reports names and set/missing status without displaying values.

Check account recovery

Sign out, select Forgot password? on the sign-in page, and submit your account email. Open the local mailbox at 127.0.0.1:55424. Follow the recovery link, set a new password, and sign in again. This mailbox is local test infrastructure.

Stop local services

Stop the application with Ctrl+C, then run:

bunx supabase stop

Supabase preserves local data. Use bunx supabase db reset only when you intend to discard disposable local data and reapply migrations.

Next, connect a subscription or find your feature’s edit point.

On this page