Ordinum Website
Marketing site for ordinum.org. Ordinum is building continuous security testing for software, firmware and hardware: it reproduces failures, checks the engineer's fix and turns confirmed cases into tests for future releases. It runs on your machines as a CLI with Python integrations, and evaluations are guided by the founders (no hosted product, no self-serve install). It is research-stage:
- ROS 2 / Nav2 in simulation is Built & validated.
- PocketBase (one host), MQTT (Eclipse Mosquitto 2.0.22 with a NanoMQ 0.25.7 edge bridge) and a four-process testbed are Built, experimental, at the stable checkpoint
768a9b5.
- Our own agent and transaction reference applications are Built, experimental, at the release candidate
ordinum-2-release (code gates at 5a05996).
- Firmware, native fuzzing, devices and physical hardware are Planned.
Pages:
- home: hero, the flagship recording with a five-step strip and a before/after result card, the workflow diagram, four product areas plus the planned row, the agentic security loop (a labeled vision), three Labs articles, one "Request an evaluation" band
- Products:
/products (one workflow #how-it-works, one engine #engine, delivery #delivery, commands, outputs, and how a run works #architecture / #lifecycle / #reproduction), /products/software, /products/agents (AI agent security), /products/robotics, /products/transactions (Transaction assurance), /roadmap
- Demos:
/demos (the flagship PocketBase recording at the top, #demo-flagship, then the other runs) and /demos/nav2-walkthrough
- Ordinum Labs:
/labs (published articles, newest finding first, plus an evidence-and-sources block) and /labs/[slug] (typed articles in lib/labs.ts)
- Evidence packages:
/evidence/[case] (manifest in lib/evidence-packages.ts; files in public/evidence/<case>/)
/security (deployment, data handling, network isolation per integration #network, operating limits, hosted CI, reporting), /about, /contact (Request an evaluation)/terms and /privacy: interim legal pages (see Legal pages)- Old URLs (
/product, /technology, /research, /vision, /demo, /solution, /how-it-works, /problem) redirect in one 308 hop (next.config.ts); /technology goes to /products#architecture.
All copy lives in lib/content.ts. See CLAUDE.md for the project structure, conventions and the rules for technical claims.
Stack
- Next.js 15 (App Router) + React 19 + TypeScript (strict)
- Tailwind CSS v4 (design tokens in
app/globals.css via @theme)
- Motion (
motion/react) for animation
- Supabase for contact-form inquiries (written by a server action)
- Resend for optional new-inquiry email notifications (plain
fetch, no SDK)
- Playwright for smoke tests, claims checks and screenshots
- Hosted on Vercel
Local development
Requires Node.js 20+.
npm install
cp .env.example .env # then fill in the Supabase values (Resend is optional)
npm run dev # http://localhost:8080
Other scripts:
| Command | Description |
|---|
npm run build | Production build |
npm run start | Serve the production build |
npm run lint | Run ESLint |
npm run typecheck | Run tsc --noEmit |
npm test | Playwright tests against next start on port 3000 (build first) |
npm run screenshots | Full-page and per-section screenshots (SHOTS_DIR sets output; SHOTS_ROUTES, SHOTS_WIDTHS, SHOTS_MODES, SHOTS_EXTRAS=0 filter) |
First Playwright run: npx playwright install chromium. If Chromium's system libraries are outside the default path, set PLAYWRIGHT_CHROMIUM_LIBS (see playwright.config.ts). If port 3000 is busy, set PLAYWRIGHT_PORT.
This is the beginning of the README. Read the rest at the original. Read the full README ↗
