The Full Install Guide

From Fork to Live in an Afternoon

Everything you need to get your own 8 Edges Operating System running: a GitHub fork, a free Supabase project, one SQL script, a handful of keys, and a Vercel deploy.

Before you start

You need four free accounts and about an hour:

A GitHub account, to fork the repo
A Supabase account, to host your database (free tier is fine)
A Vercel account, to host the app (free tier is fine)
An Anthropic API key, to power the agents (pay as you go)

Step 1: Fork the repo

Open github.com/talentedgeai/8edges and click Fork. Your fork carries the whole app: the three portals, the workflow library, the agent endpoints, and the database migrations.

If you plan to customize locally:

git clone https://github.com/YOUR-USERNAME/8edges.git
cd 8edges
npm install
cp .env.example .env.local

Step 2: Create your Supabase project

Sign in at supabase.com and create a new project. Any region, any name.
From Project Settings → API, copy the project URL, the publishable key, and the secret key. You will paste them in step 4.

Step 3: Install the database

In your Supabase project, open the SQL Editor.
Open supabase/schema.sql from your fork, paste the whole file, and click Run.
When it finishes, open the Table Editor and switch the schema selector to company_os. You should see 148 tables: people, deals, invoices, goals, coaching, and the rest. The Data Atlas is the interactive map of what you just installed.

The script is idempotent: if a run is interrupted, run it again. It creates the company_os schema, every table, the rules baked into the database (for example, a key result cannot be saved without an accountable human), and the roles the data assistant uses.

Step 4: Set your keys

Nine required values in .env.local (and later in Vercel). Everything else in .env.example is optional.

Key	Where to get it
`SUPABASE_URL`	Supabase → Project Settings → API → Project URL
`SUPABASE_SECRET_KEY`	Same page → secret key. Server only, never exposed to the browser
`NEXT_PUBLIC_SUPABASE_URL`	Same project URL again, for the browser auth client
`NEXT_PUBLIC_SUPABASE_PUBLISHABLE_KEY`	Same page → publishable key
`ADMIN_EMAILS`	Comma-separated emails allowed into the admin portal. Start with yours
`ANTHROPIC_API_KEY`	console.anthropic.com → API Keys
`OPENROUTER_API_KEY` + `OPENROUTER_MODEL`	openrouter.ai → Keys, plus a model slug
`CHATBOT_DB_URL`	A Postgres connection string using the `chatbot_reader` role the install script created
`CRON_SECRET`	Any long random string. Vercel sends it as a bearer token to the cron endpoints

Step 5: Deploy to Vercel

In Vercel, choose Add New → Project and import your fork.
Paste the same environment variables into the project settings.
Deploy. First build takes a few minutes.
Open your deployment URL, sign in with an email from ADMIN_EMAILS, and you are in your own admin portal.

Step 6: Turn on the agents

The 13 scheduled agents are defined in vercel.json and start running automatically onceCRON_SECRET is set: the coaching cycle, onboarding, review triggers, contractor payments, QuickBooks sync, the digests, and the campaign sender. To disable one, delete its entry fromvercel.json and redeploy.

Optional integrations

Each of these switches on a feature when its keys are present, and stays silently off when they are not:

Resend (RESEND_API_KEY): transactional and marketing email
Stripe (STRIPE_SECRET_KEY): payments and checkout
QuickBooks (QBO_CLIENT_ID, QBO_CLIENT_SECRET): invoice sync and P&L
Lark (LARK_APP_ID, LARK_APP_SECRET): team messaging and webhooks
Telegram (TELEGRAM_BOT_TOKEN): notifications
GitHub (GH_PAT): repo sync features

Stuck?

The $99 community exists exactly for this: working sessions, install help, and direct answers. Or schedule a consultation and we will install everything for you.