e11

The platform · 17 active

The full fleet directory.

Eleven11 is a platform, not a product. Surfaces are what customers and our team open every day. Engines run the work in the background. Tooling is the operator and partner control planes that connect them. Every name below is shipped, named, and operated by the same principals.

Each product carries its own subdomain, its own image, its own deploy pipeline. The names below link to the live surface where one exists, and to consultation where access is partnered or gated.

Fleet shape

Surfaces

09

Engines

03

Tooling

05

Surfaces · 09 active

What customers — and we — open every day.

What customers and our own team open every day. Tenant-facing UIs.

01 · Operating canvas

LIVE

architect

The thinking surface where infrastructure decisions begin, lock, and compound.

A workspace that sits above the tools and above the operator. Three loops on one canvas — think, operate, remember — with a memory spine that makes prior context recall-visible. Less dashboard. More drafting table.

Read the one-pager

02 · Attack surface intelligence

LIVE

dhara

Know your public footprint before a scanner or a competitor does.

Continuous attack surface monitoring with ranked findings and structured reports. Each scan feeds an intelligence graph that gets sharper with every target.

Read the one-pager

03 · Public canvas

LIVE

manch

Sign up. Make a board. Share a link. Eleven11's first walk-up product.

A tldraw-shape collaborative canvas that anyone on the public internet can sign up for, board on, and share. The first sibling without CF Access gating — a PLG funnel from anonymous viewer to authored board to memberful workspace.

Read the one-pager

04 · Sovereign data tables

LIVE

kosh

Airtable-shape tables on your own per-tenant Postgres. Owned, not rented.

Typed tables, saved views, CSV/XLSX import, Notion-style page drawer — running inside your tenant box, not on someone else's multi-tenant cloud. The data layer Architect, alerts, and outreach all read from.

Read the one-pager

05 · Visual production

LIVE

studio

Launch-Design carousels, reels, and banners — rendered, queued, and published.

Remotion-powered Instagram and LinkedIn pipeline with a render worker, asset CDN, and direct Graph-API publish to Eleven11 and Dhara handles. Sibling to PR — the visual editorial spine to PR's text one.

Read the one-pager

06 · Research substrate

LIVE

granth

PDFs, ebooks, and corpora — parsed, embedded, and queryable from your workspace.

A NotebookLM-style research substrate on your own infrastructure. Recipe-driven ingestion of PDFs and ebooks, sovereign embeddings via the Dhara Ollama endpoint, BYOK query LLMs, and one-click promotion of citations into Architect's memory units.

Read the one-pager

07 · Sovereign mail

LIVE

mailbox

Owned IMAP, SMTP, and webmail — a real mail product, not a forwarding alias.

Mail hosted on Eleven11 infrastructure with branded webmail, programmable provisioning, BIMI-ready DMARC posture, and a control plane that doesn't depend on Google or Microsoft. Built so the mail you depend on isn't somebody else's policy decision.

Read the one-pager

08 · Publishing surface

LIVE

blog

A branded, SEO-ready blog deployed to your domain. No CMS to manage.

Standalone blog consumer that receives signed content from the PR pipeline and renders it with full metadata, JSON-LD, sitemaps, and canonical URLs baked in. One pipeline, many branded surfaces — each deployed and managed from Operator.

Read the one-pager

09 · Platform rebuild

BETA

punah

Legacy WordPress sites rebuilt as modern, maintainable infrastructure.

Recipe-driven capture, typed records, and a rebuild pipeline staged at your subdomain before you commit. The platform carrying business risk gets properly replaced.

Read the one-pager

Tooling · 05 active

What ties the surfaces and the engines together.

Operator and partner control planes. The plumbing between surfaces and engines.

13 · Admin plane

PARTNER

operator

One UI aggregating every service — pr, cal, alerts, outreach, discovery, dhara, mail.

The internal control plane Eleven11 uses to operate its own platform. Server-rendered pages that fetch live state from each upstream API on every request — no stale dashboard. Available to partners running Eleven11 stacks under their own brand.

Read the one-pager

14 · Capture operator

PARTNER

tira

The control plane for your content capture and rebuild pipeline.

Recipe-driven scraping operator that manages ephemeral workers, tracks capture jobs, and surfaces cost events. Every Phoenix rebuild and content migration runs with full visibility from a single UI.

Read the one-pager

15 · Outreach engine

PARTNER

outreach

Campaigns, scans, teasers, and signed sends — all on owned infrastructure.

The operator-side engine that turns a Dhara teaser or a Discovery finding into a sequenced, audit-trailed outreach. Owned mail transport, WhatsApp Business handles, opt-in/out plumbing, queue-and-drain workers. Built for partners, not as a customer-facing UI.

Read the one-pager

16 · Event bus

LIVE

alerts

Platform events, six-channel dispatch, persistent history. Producers fan in, channels fan out.

Every service in the fleet posts normalized events; alerts routes them through SMTP, signed webhooks, Telegram, Slack, Discord, or SMS — with retry semantics, persistent history, and per-event routing rules. The nervous system of the platform.

Read the one-pager

17 · Privileged access tier

LIVE

break-glass

Sovereign WireGuard-gated tier for emergency operations and incident response.

A separate trust zone, hardware-key authenticated, hub-and-spoke topology, no dependence on third-party SSO. The path that lets us guarantee customer mailbox recovery, mail platform availability, and incident response when an external auth provider has a bad day.

Read the one-pager

How it fits together

The fleet as one nervous system.

Every surface publishes a widget contract and a resources endpoint. Architect consumes both — a Dhara finding becomes a canvas tile, a Cal availability check becomes an inline answer in a session, a Kosh table view becomes a matter section.

Every engine emits normalized events into alerts. Every operator and partner action is logged in the same place a customer-visible event is. There is one substrate underneath, and the same principals operate it.

The privileged-access tier sits below all of it — a sovereign, hardware-key-authenticated path that doesn't depend on any external SSO. It's the reason mailbox recovery, mail platform availability, and incident response stay on our terms even when a third-party provider has a bad day.

Talk to the engineers

The fleet runs because the engineers run it.

Most of these products are partner-gated by design. Use the consultation route to discuss access, partnership, or how the fleet might shape your platform.

Direct line

Consultation requests stay owned. We reply from e11 after reviewing fit and timing.