GUIDED TOUR
Understand AENET in 3 layers
A guided tour with three depths: 30 seconds, 3 minutes and 15 minutes. Choose the layer that matches how much time you have.
30 seconds
AENET is a private AI ecosystem being built in public. This website is the read-only public observation layer: it publishes sanitized snapshots, a bounded public API and an anonymous traffic channel — and nothing can reach the private AENET Core from here.
3 minutes
The public side is a pipeline: sanitized snapshots from the core are published through a one-way gateway to static pages, a versioned public API (v1), a glossary, research and a development log. A separate early-access waitlist is the only public write path, and it is fail-closed. The private core — agents, model routing, memory, spine — is never reachable from the public side.
15 minutes
Follow the guided steps below: what AENET is, the problem it solves, the architecture, one full workflow through the systems, the verified build evidence, and how to request early access. Each step links to the real page with the full detail.
What is AENET?
An ecosystem being built in public: a private core observed through a public, read-only gateway.
What problem is it solving?
Building an AI ecosystem without a public attack surface: a strict one-way boundary, sanitized snapshots, and no control channel to the core.
How the architecture works
Public gateway, snapshot layer, public API, time, glossary, research and development flow — each with a bounded role and a one-way data direction.
How one workflow moves through AENET
A visit flows: sanitized snapshot → static page + public API → anonymous traffic event. An early-access request flows: form → Turnstile → intake shield → D1 waitlist — never into the core.
What has actually been built
Verified public states only: the gateway is live, the public API serves v1, the snapshot layer publishes, and the development log records each version — with evidence links on the build page.
Request Early Access
Join the first public testing queue. It is a waitlist — not an account system — and it is the only public write path, protected by Turnstile and fail-closed.