The platform

Elf is a plugin system.

Not a suite of products that happen to share a logo. A host, and things that plug into it — a knowledge base, a design editor, a browser, a control layer for agents. They are separately built and separately deployed, and they run as one because they share one identity.

Every figure on this page was verified against a live system on 1 August 2026.

What plugs in

Five surfaces, honestly labelled

Each one says what it is and where it actually stands. A slot that is not filled yet is named as an empty slot, not implied to be finished.

The host

Elf

Identity, account, billing, and a managed cloud relay to the models. Everything else plugs into it and authenticates against it.

Live

Knowledge

Folio

A local-first, Notion-compatible knowledge database — documents and database views. Serves 24 tools to a connected agent.

Live · folio.elf.danceRead the reference →

Design

OpenPencil

A Figma-compatible design editor, open source by Danila Poyarkov — we run a fork wired into Elf sign-in. Its 90 tools let an agent create and modify design nodes directly, rather than describing changes for a human to make.

Live · design.elf.danceRead the reference →

The web, as a capability

Elf browser

A first-party browser plugin rather than a bolted-on scraper — so a session, its tabs and its history are part of the same runtime as everything else.

In the desktop app

The control layer

Agent Fabric

Hands work to agent harnesses and keeps a verifiable record of what ran. Staging only today — the reference page says exactly which lanes work and which do not.

Staging onlyRead the reference →

Why it composes

One identity, verified — not assumed

Separately deployed

Folio and OpenPencil are their own repositories and their own deployments. Nothing is a monolith pretending to be modular.

One signed identity

Each verifies RS256 tokens against Elf’s live public key endpoint. Signing in once is what makes them one product rather than three.

Fails closed

If that verification is not configured, the service refuses to start rather than quietly accepting anyone. Absence is an error, not a default.

Underneath

One governed path to the models

134models served
7live providers
90design tools
24knowledge tools

Model figures were read from a live authenticated request to the gateway on 1 August 2026, not from a catalogue file. Tool counts are what a connected client can actually call — where a registry lists more than the server serves, the smaller number is the one printed here.

What this page does not claim

The other half of an honest spec sheet

  • That the control layer runs in production. Its production flag is off.
  • That any of this is proven at scale. It is not, and we do not have the numbers to pretend otherwise.
  • That the coding-assistant surfaces are available. They are built and gated dark.
  • Any uptime, SLA, or user-count figure. We cannot produce them honestly.

Start with the part that works.

Elf is the host, and it is live today — chat, browse, read docs, and keep your thread. The rest plugs in as it lands.

Go to elf.dance