Run locally
Start Hikari with local Supabase and reach your first signed-in Dashboard.
Install Bun 1.3.14, Node.js 20.19 or later, and a Docker-compatible runtime. This path starts a fresh local application; it does not migrate an existing Hikari deployment.
Clone and install
git clone https://github.com/coremvp/hikari.git
cd hikari
bun installRun the following commands from this repository root.
Start local Supabase
bunx supabase start
./coremvp env syncSupabase 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.
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 devOpen 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 stopSupabase 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.