Type
Tech stack
Connected services
Documentation
Full
Setup, architecture, and how the pieces fit together.
Maintenance
Occasional
Occasional fixes, but no active roadmap.
Description
Speculative zero-latency edge engine — branch prediction for the cloud.
Pre-revenue. Diligence-ready. The asset is the runtime IP, Cloudflare reference edge, and acquirer-shaped adapters — not ARR.
Predict the next API/tool call → pre-execute on a COW branch (shadow side effects) → commit on hit (~0ms) or roll back on miss.
Live demo
Open the playground: https://phantominfra-edge.matthewlooney5.workers.dev
No install. Pick a case (Browse, Quote, Checkout, Inventory, Support, Agent, Search), speculate, confirm — or Tour all. Click Prove it for a live HIT vs MISS speedup.
GitHub Pages front door (enable Settings → Pages → Deploy from branch → /docs): docs/index.html — points at the live Worker.
Why it matters
| Proof | Where |
|---|---|
| ~1000×+ hit vs miss (demo bench) | npm run bench |
| Workers + DO + KV mesh | apps/edge |
| Cloudflare / Vercel / Node adapters | @phantominfra/adapters |
| Whitepaper + acquisition + IP | docs/whitepaper.md, docs/ACQUISITION.md, docs/IP.md |
| Threat model | SECURITY.md |
| Audit export | engine.exportAuditBundle() / GET …/audit |
Monorepo (v1.4.2)
| Package | Role |
|---|---|
@phantominfra/runtime | Engine, predictor, policy, ledger, value/audit |
@phantominfra/sdk | HTTP + SSE client |
@phantominfra/adapters | Workers / Vercel Edge / Node drop-ins |
@phantominfra/web | Landing + demos |
@phantominfra/edge | Cloudflare production-shaped reference |
Quick start (local)
Local API key: dev_phantom_key · OpenAPI: /openapi.json · Deploy: DEPLOY.md · Live notes: docs/LIVE.md
Adapter sketch
Diligence / IP
- Acquisition brief
- Data room index
- IP inventory
- IP assignment outline
- Term sheet outline
- Patent / trade-secret notice
- Commercial license · Evaluation license
- Whitepaper
- One-pager (Print → PDF)
- Changelog
- Brand:
brand/logo.svg·brand/wordmark.png
License
FAQ
- What accounts or services do I need to run this?
- For the local runtime, you only need Node.js and the dev API key included in the repo. The live demo runs on Cloudflare Workers, but that's optional, the core engine works standalone. If you want to deploy to production, you'll need a Cloudflare account to use the Workers reference implementation.
- What is the tech stack?
- Node.js runtime with adapters for Cloudflare Workers, Vercel Edge, and plain Node. The core engine is the predictor and policy layer; the monorepo includes the SDK (HTTP + SSE client), adapters, and a web demo. No external dependencies are required to run the engine itself.
- How do I get it running locally?
- Clone the repo, use the dev API key `dev_phantom_key`, and start the local API. The OpenAPI spec is at `/openapi.json`. See DEPLOY.md for deployment steps and docs/LIVE.md for current notes.
- What documentation and support are included?
- Basic documentation covers setup and the adapter patterns. The repo includes a whitepaper, threat model (SECURITY.md), and audit export capability. This is pre-revenue, pre-maintenance software, no ongoing support or updates are guaranteed.
Domains
Seller
Reviews
No reviews yet.