Every run returns a proof.
Not a policy page. A trace. Every stage recorded, every run attested.
- Prompt
- Routed
- Executed
- Attestation
- Retention
Sealed before it leaves
Encrypted on your device, against your key. Never written to disk in plaintext.
Routed to a verified operator
Pin a region or let the network route it. The route is stated before you send.
Executed inside an enclave
The operator owns the hardware and still cannot read the workload on it.
Attested, then discarded
An attestation you can check. Retention none — no copy left to leak.
Two models. One policy: yours.
Open weights, your policy. Inlex Edge for low-latency edge work, Inlex Core for frontier capability.
- Inlex EdgeFast edgeLow-latency, runs in-enclave
- Inlex CoreUnfilteredFrontier capability, no vendor filter
- ExecutionSealedHardware-attested enclave
- Context256KTokens per thread
- Your usage policy, not the vendor's
- Enclave execution
- Prompts never leave your key
- You hold the weights and the keysVaries
- Decentralized operator network
- Per-run attestation
- Context window256K128K
- Open weightsVaries
Inlex Vault
Threads outlive sessions. Persistence without giving up custody.
- 01EncryptSealed on the device against your key
- 02FragmentSplit into shards, none of them whole
- 03DistributePlaced across independent operators
- 04VerifyContinuous storage proofs, on chain
What that gets you
- Encrypted end to end
- Sealed against your key before it is fragmented. Storage never sees plaintext.
- Fragmented and distributed
- No operator holds a whole object. Compel one and there is nothing to hand over.
- Verifiable by proof
- Storage proofs published continuously. You check, rather than trust.
- Content-addressed
- Addressed by hash, so tampering is arithmetic rather than opinion.
Rotation happens in place.
A workspace, not a chat window. Threads, keys, routes and proofs are all inspectable.
- 01The composerAsk anything. Nothing leaves your key. The status strip states the route before you send.
- 02Threads and proofEvery answer carries its operator, its attestation and its latency.
- 03Key rotationEvery 30 days, or immediately on device loss. Re-sealed in place, no plaintext written.
- 04Operator selectionPin a region, force local execution, or auto-route. The operator set is public.
Priced by the run.
Every tier runs in an attested enclave. Only headroom and seats change.
For evaluating enclave execution on real work
- Pay in $INLEX for 10% off
- Private threads in an attested enclave
- 5 GB encrypted storage, anchored to your key
- Standard daily allowance
- Per-run attestation on every response
- Up to three integrations
For daily work that deserves more headroom
- Pay in $INLEX for 10% off
- 10× the Starter daily allowance
- 50 GB encrypted storage, anchored to your key
- Operator pinning and region restriction
- Prepaid 30-day periods, unused days carry over
- Priority support, 24/7
For dedicated enclaves, compliance and scale
- Pay in $INLEX for 10% off
- Daily limits set to your workload
- Admin dashboard, 10 seats included
- 200 GB shared encrypted vault
- Dedicated enclave clusters with auditable attestation
- Data residency and custom retention policy
- Full API access for private deployments
$INLEX settles the work.
A meter, not a story. Jobs settle in it, operators bond it, revenue buys it back.
Read the tokenomics- 01A customer paysEvery job on the network settles in $INLEX.
- 02Operators run enclavesServing compute requires a bond, which locks supply.
- 03Compute cost settles60% of revenue pays the operators who did the work.
- 04Revenue buys back20% is used for open-market $INLEX buybacks, monthly.
- 05Usage locks supply20% funds operations. The company holds no allocation.
What is built, and what is next.
Dates, not adjectives. A phase closes when its milestones are verifiable.
Phase one
Completed- Enclave-first backend and attested API fabric.
- Operator network and per-run attestation.
- Core model infrastructure and inference pipeline.
- Zero-retention telemetry.
- Closed preview with launch partners.
- Public preview of the Inlex workspace.
- Sub-2s enclave response at the median.
- Standardised hardware attestation format.
Phase two
In progress- Unified workspace with encrypted control surfaces.
- Expanded early access and production feedback.
- Personalisation that retains context without retaining data.
- Mobile client tunnelling to live enclaves.
- Multi-agent orchestration inside a single enclave.
- Voice input processed entirely in-enclave.
- Developer SDKs for custom enclave modules.
- Inlex Vault general availability.
Phase three
Planned- Global operator hubs with latency guarantees.
- Federated execution at the edge, without data escape.
- Local-first execution unified with private memory.
- Operator certification programme.
- Cross-chain settlement for borderless workflows.
- Marketplace for third-party enclave modules.
- Private predictive models for regulated sectors.
- Sovereign cloud: a distributed, encrypted compute mesh.
Frequently asked.
If it is not answered here, the docs go deeper.
Intelligence Without Censorship
Open the workspace and send one prompt. The trace tells you where it ran.
Run private