Brings 0pt to the SIAX repo standard. README, LICENSE (proprietary, correct
for this repo), Dockerfile and .gitea/workflows/ci.yml already existed and are
left untouched; no .github/workflows exists.
The architecture document was written by reading the code (entrypoints,
routes, services, migrations, Dockerfile, env, tests) and by probing the live
0pt.app instance -- not from the templates. It therefore contradicts the
existing docs in several places, deliberately:
* /api/0pt/* answers ANONYMOUSLY in production (live-verified 2026-08-07):
GET https://0pt.app/api/0pt returns 200 with no token, and 200 with a
deliberately invalid one. The deployment is current (the newer lakehouse
routes are present), so middleware.ts is simply not running. README lines
49-52 and merge 6531384 claim the opposite. Root cause UNKNOWN -- flagged,
not guessed.
* No handler reads x-0pt-verified-tenant. middleware.ts sets it; nothing else
in the repo reads it. Every /api/0pt/* handler takes tenant_id from the
request body/query instead, so tenant isolation is not implemented.
* Everything outside /api/0pt/* has no auth at all (matcher scope), including
GET /api/admin/metrics and GET /api/orders (both live-verified 200 anon) and
POST /api/payments/{id}/release, which flips an order to "delivered"
regardless of payment.
* CL0UD policy client is fail-open and AUD0 audit is a silent no-op when their
URLs are unset, with no production guard -- unlike AUTH_ENFORCE, which has one.
* connections/db-grant documents AES-GCM encryption it does not implement.
* The FastAPI engine (services/api) has zero authentication despite
lib/engine.ts sending X-Internal-Token.
* services/scrapers/waf_bypass.py (FlareSolverr, Tor, cloudscraper, proxy pool,
undetected browser, fake identities) plus flaresolverr/tor-proxy in
services/infra/docker-compose.data-stack.yml directly contradict CLAUDE.md
§1 and the README's compliance claim. Left in place -- deletion is a Simon
decision, recorded as open question 2.
* Production has NO database (live /api/health reports db:not_configured) and
the whole /api/0pt/* capability layer is per-module in-memory Maps, so state
does not survive a cold start and is not even shared between route modules.
siax.config.json deviates from the template on two fields, on purpose:
deploy.target is "vercel" (live-verified Server: Vercel header), not "coolify",
and designSystem is null because @siax/ui is not a dependency here. Both
deviations are documented in ARCHITECTURE.md §5 and §8.
Docs-only change. No code, CI, LICENSE or workflow files were modified.
72 lines
3.9 KiB
Markdown
72 lines
3.9 KiB
Markdown
# 0pt — your data
|
|
|
|
Data services on demand for the Nordics + Europe. Compose a data job, pay 50 % to start,
|
|
watch production live, validate with full provenance, deliver anywhere. Owned by **SIAX
|
|
Technology AB**. Honest accuracy is the moat: every field carries source, freshness and
|
|
confidence; nothing is guessed.
|
|
|
|
**Live:** https://0pt.app · **Contract:** [`CLAUDE.md`](CLAUDE.md) + [`docs/`](docs/)
|
|
|
|
> **Architecture (verified against code, not aspirational):**
|
|
> [`docs/architecture/ARCHITECTURE.md`](docs/architecture/ARCHITECTURE.md).
|
|
> It documents the real API surface, the real persistence story, and the known
|
|
> security gaps — including several places where this README is optimistic. Read
|
|
> it before trusting any capability claim below. Repo identity + estate
|
|
> classification: [`siax.config.json`](siax.config.json).
|
|
|
|
## Two planes (see [docs/02-architecture.md](docs/02-architecture.md))
|
|
|
|
- **Edge (Vercel, this app)** — marketing, catalog, the order lifecycle, customer portal,
|
|
admin portal, and the API route handlers. Defers to the data engine when `ENGINE_URL` is set.
|
|
- **Engine (`services/api`, runs on a VPS)** — FastAPI orchestrator + worker pipeline doing
|
|
the **compliant** sourcing (official API → bulk → authorized web → licensed → else level 0).
|
|
Never on Vercel (long jobs). Bypass/stealth/proxy-rotation/fake-account paths are excluded
|
|
by design (CLAUDE.md §1).
|
|
|
|
## Routes
|
|
|
|
| Area | Routes |
|
|
|---|---|
|
|
| Marketing | `/` (hero, filosofi, katalog, motorn, visualiseringar, täckning, editorial, bevis, priser, footer) |
|
|
| Catalog | `/katalog`, `/katalog/[id]` |
|
|
| Sourcing map | `/kallor` |
|
|
| Order lifecycle | `/bestall` → `/bestall/forskott` → `/order/[id]` → `/order/[id]/validera` |
|
|
| Customer portal | `/portal`, `/portal/subscriptions`, `/portal/files`, `/portal/integrationer`, `/portal/settings` |
|
|
| Admin portal | `/admin`, `/admin/sources`, `/admin/jobs`, `/admin/customers` |
|
|
| API | `/api/{health,estimates,catalog,sources,orders,orders/[id],subscriptions,admin/metrics,uploads,auth/*,payments/*,webhooks/stripe,connections/db-grant}` |
|
|
|
|
## Design system
|
|
Mono/editorial, light, radius 0, Inter + JetBrains Mono, single red `#e40014`, animated grain,
|
|
scroll-reveal motion. **No photography** — imagery is rendered data (`DataArtifact`). Every fact
|
|
shows a provenance square (`ProvenanceBadge`). Full spec: [docs/05-design-system.md](docs/05-design-system.md).
|
|
|
|
## Run locally
|
|
```bash
|
|
pnpm install
|
|
pnpm dev # Next.js on http://localhost:3000
|
|
|
|
# data engine (separate, optional)
|
|
cd services/api && pip install -r requirements.txt && uvicorn orchestrator.main:app --reload
|
|
```
|
|
|
|
## Deploy
|
|
- **Frontend** → Vercel (project `0pt`, scope *Simon Axelsson's projects*), domain `0pt.app`.
|
|
- **Engine + DB + embeds** → one VPS via [`infra/docker-compose.yml`](infra/docker-compose.yml) (Postgres+pgvector, Redis, api, worker, NocoDB, Metabase, Caddy).
|
|
- Env inventory: [`.env.example`](.env.example).
|
|
- **Auth on `/api/0pt/*` is fail-closed**: with `AUTH_ENFORCE` unset the middleware
|
|
REQUIRES a verified Zitadel Bearer token (401 without one). Only the literal
|
|
`AUTH_ENFORCE=false` disables it, and that is refused when `NODE_ENV=production`
|
|
(the process throws at startup rather than serving anonymously).
|
|
|
|
## Status
|
|
Frontend, full order lifecycle, customer + admin portals, edge API, payment/auth/embed
|
|
infrastructure, the compliant data engine, schema and infra are all in place and building green.
|
|
Integrations are env-guarded and activate when their keys/DB are provided:
|
|
|
|
1. **Database** — Vercel → Storage → Postgres (sets `POSTGRES_URL`) → durable persistence (schema in [`sql/001_init.sql`](sql/001_init.sql)).
|
|
2. **Stripe + Resend** keys → payments + email.
|
|
3. **VPS** for the engine → set `ENGINE_URL`.
|
|
4. **`AUTH_SECRET` + `DEV_LOGIN_KEY`** → login (full OAuth via Auth.js lands with the DB).
|
|
|
|
© 2026 SIAX Technology AB. Not affiliated with Protosell.
|