100 TRILLION TOKENS. EVERY DAY.
Free coding intelligence for developers.
PROJECT ZERO · DEVELOPER ALPHA
THE ZERO POOL IS COMING.
tessen/project-zero
⭐ Star this repository to follow the opening of the ZERO Pool.
Tessen · Project Zero · OpenCode · Node · FAQ
We want to find out.
Project Zero is Tessen's developer experiment: open a shared pool of coding intelligence, make it free during the Alpha, put it where developers already work, and see what they build.
The first Zero Pool is planned to start at:
100,000,000,000,000 TOKENS / DAY
RESET 00:00 UTC
That's 100 trillion shared tokens every day.
No waitlist theater. No fake usage counters. No invented capacity.
When the Alpha opens, the goal is simple: pick ZERO, point it at a real repository, and build.
OpenCode is the first distribution focus for Project Zero.
The canonical developer-facing model reference is:
tessen/project-zero
We want ZERO to fit into an agentic coding workflow developers already understand rather than requiring a new editor.
The exact public install, authentication and selection instructions will appear here as soon as the clean external-developer path is certified. Until then, this repository will not publish placeholder commands that look real.
Follow the OpenCode launch path →
The Alpha launches around one shared daily pool:
100T tokens/day · $0 developer price during the preview · reset 00:00 UTC.
100T is the planned launch baseline for the shared Project Zero pool — not 100T per developer and not a promise of unlimited compute.
Tessen can apply fair-use allocations, concurrency controls, eligible routing, abuse protections and operational limits so the pool remains useful.
That's part of the experiment.
When public telemetry is certified, Project Zero can publish real pool usage, remaining capacity and reset information. Until then, we will not simulate those numbers.
Project Zero is designed as a network loop, not just a free model promotion.
100T DAILY ZERO POOL
↓
DEVELOPERS BUILD
↓
MORE DEVELOPERS JOIN
↓
MORE TESSEN NODES JOIN
↓
MORE VERIFIED COMPUTE CAPACITY
↓
NEXT ZERO POOL CAN GROW
Developers can optionally run Tessen Node and explicitly opt compatible compute into the network.
If Tessen verifies additional available capacity, the next day's published Zero Pool can increase above the 100T baseline at the 00:00 UTC reset. Any increase must come from real server-authoritative capacity/accounting data — never a marketing multiplier.
Node participation remains explicit. Any credits or benefits must be tied to real contributed work. Project Zero does not promise guaranteed earnings.
Project Zero does not need every future Tessen developer feature to be finished before the Alpha can open.
It does need the core experiment to be real.
A completely new developer should be able to:
- discover ZERO;
- authenticate with Tessen;
- receive Project Zero access;
- use ZERO from a supported coding workflow;
- select
tessen/project-zero; - complete a real coding request;
- return later with the same identity and access.
Node participation is optional and comes after the coding experience works.
That is the opening gate.
Project Zero Alpha is being prepared around:
- $0 access during the preview;
- a 100T shared daily baseline;
- a daily 00:00 UTC reset;
- OpenCode-first developer distribution;
- the stable
tessen/project-zeropublic identity; - real request, usage and underlying cost accounting;
- fair-use, rate, concurrency and abuse controls;
- operational kill switches;
- truthful status and failure states;
- optional Tessen Node participation.
Free does not mean unmetered or unlimited.
Once production telemetry is ready, we want the interesting questions to be visible:
- How many developers actually activate ZERO?
- How many complete a real coding task?
- How much of the daily pool gets used?
- How many developers come back?
- How much verified capacity is contributed by Nodes?
- Can the next Zero Pool grow?
We will publish those numbers only when they are real.
Our long-term ambition is 100,000 activated developers. That is a target, not a current-user claim.
An activated developer means more than a signup: a developer who completes a successful real ZERO coding request.
Project Zero is a public developer program from Tessen.
Tessen coordinates identity, entitlement, routing, accounting, reliability controls and operational safety behind ZERO. This repository is the public Project Zero launch, documentation and community home; it is not a dump of Tessen's private platform source.
Read the public architecture →
Tessen Node is designed to run wherever useful compute already exists — on a developer's computer, a Linux server, a VM, or eventually infrastructure operated by cloud and hosting providers.
These are target requirements for the public Node program, not a claim that every configuration at these limits has already been certified.
| Environment | Initial target |
|---|---|
| Windows desktop | Windows 10/11 64-bit · 2+ CPU cores · 4 GB RAM · 5 GB free disk · outbound HTTPS |
| Linux server / cloud | Ubuntu 22.04+ · x86_64 initially · 2+ vCPU · 4 GB RAM · 5 GB free disk · outbound HTTPS |
| GPU | Optional; support depends on hardware, drivers and workload |
| Headless server | No graphical desktop required; command-line/service operation |
The native Windows Node includes its own Node.js runtime, so users do not need to install Node.js or npm separately.
Node is also intended to be the local hardware/runtime layer for Tessen Code and supported OpenCode workflows:
Developer → Tessen Code / OpenCode → Tessen Node → Local hardware
Node can discover supported local hardware and available capabilities. Detection does not mean automatic execution or automatic network participation. Workloads remain subject to Tessen authorization and explicit user controls.
The long-term Node network is designed to include hosting companies, VPS providers, dedicated-server operators, GPU providers and other infrastructure partners. Eligible providers can eventually run a headless Node on their infrastructure and explicitly contribute verified capacity to the network.
A server Node does not need a graphical interface or desktop tray.
Read the complete Node requirements and architecture →
| Guide | What it covers |
|---|---|
| Project Zero | The Zero Pool and public Alpha contract |
| OpenCode | The first developer distribution focus |
| Node | How contributed compute can grow the network |
| Developer Alpha | The minimum real opening standard |
| CLI | Tessen's terminal-native path |
| Architecture | Public request-flow architecture |
| Roadmap | What remains before opening |
| FAQ | Straight answers about ZERO |
| Security | Responsible vulnerability reporting |
Right now:
THE ZERO POOL IS COMING.
When a clean external developer can complete the real Alpha path without founder intervention:
THE ZERO POOL IS OPEN.
At that point this README should lead directly into the certified OpenCode/onboarding path and real operational information.
Until then, star or watch this repository to follow the opening.
PROJECT ZERO — ZERO
100T TOKENS EVERY DAY.
MORE DEVELOPERS. MORE NODES. MORE INTELLIGENCE.