Predictech — Prediction market analytics

Web dashboard aggregating Polymarket, Kalshi, and Predict.fun with an Arkham-style dark UI: markets, volume, liquidity, spreads, and categories.

Features

• Dark / neon layout
• Live-style market views from your Supabase snapshots
• Category and search filters
• Aggregate stats
• Responsive UI

Requirements

• Node.js 20.x (see package.json engines)

Setup

1. Install dependencies

npm install

2. Supabase (dashboard reads from your project)

Create .env.local in the project root:

SUPABASE_URL=https://your-project.supabase.co
SUPABASE_ANON_KEY=sb_publishable_your_key_here

Optional: copy config.js.example → config.js if you use the Vite CONFIG pattern.

Where to find values: Supabase Dashboard → Settings → API

• Project URL → SUPABASE_URL
• Publishable key (sb_publishable_... or legacy eyJ...) → SUPABASE_ANON_KEY

Important

• Use the publishable (anon) key for the browser build.
• Do not use secret keys or the service role key in frontend code.
• For sync scripts (server-side inserts), use SUPABASE_SERVICE_ROLE_KEY in .env.local only (never commit it). See lib/supabase.ts.

3. Database schema

Apply SQL under supabase/migrations/ to your project (see supabase/README.md). Then run at least one sync so tables have data, for example:

npm run sync-polymarket

Other env vars (Kalshi, Predict.fun, etc.) are documented in config.js.example and in scripts/.

4. Run the dev server

npm run dev

Default: http://localhost:5173 (Vite may pick another port if busy).

Production build

npm run build

Output: dist/.

Repository layout

Path	Role
index.html, styles.css, app.js	UI and data loading
lib/	Supabase client (TS/JS), category mapper, i18n
scripts/	Sync jobs and Predict.fun utilities
supabase/migrations/	Postgres schema for snapshots
features/	Internal product / architecture notes (English)

Predict.fun HTTP API (reference)

Examples used by tooling: GET /v1/markets, market stats, orderbook endpoints — see Predict API docs.

License

MIT — see LICENSE.

Third-party data

Market data comes from third-party APIs and your own Supabase snapshots. Using this software does not grant rights to those datasets; comply with each provider’s terms of use.