Roadmap & availability

Emithook's v1 engine is feature-complete. Both products (relay + Send), all four ingresses, the console, the management/Send API, the full CLI, the MCP server, the TypeScript SDK, every broker adapter, and the application/subscription model + consumer portal are shipped. This page is the single source of truth for what you can call today; if you're an agent, read it before driving the API, CLI or MCP server.

Availability legend

The same badges appear throughout the docs:

• Available Shipped — you can call it today.
• Roadmap Not yet shipped — see What's remaining below. Roadmap surfaces return not_implemented until they land.

What's shipped Available

Everything below is live:

• Core engine — Cloudflare Worker edge (presets, handshakes, custom domains) as a pure accept-always buffer → durable queue, with verify-as-verdict in the processing plane. One Fair-Queue delivery path with backoff/jitter, circuit breaker, Standard Webhooks signing, idempotency, claim-check, SSRF gate. Hardened event store, hourly per-endpoint archive, logs, replay (incl. restore/replay from archive), and the Pull API.
• All four ingresses — the HTTPS edge, queue ingestion across every broker adapter (SQS/SNS, Pub/Sub, Azure Service Bus/Event Hubs, AMQP, Kafka/Redpanda, NATS, Redis Streams), inbound email (the MX engine + agent inbox), and the Send API.
• Tenant experience — the console (dashboard, endpoint wizard, log explorer, replay, secrets, alerts), self-service onboarding, custom domains, filters + sandboxed JS transformations, and the expanding provider-preset catalog.
• Send — the Send API, the application/subscription model + consumer portal, FIFO endpoints, and the queue-adapter framework in both directions.
• Tooling — the full CLI, the MCP server (query + write + the LLM-readable inbox tools), and the TypeScript SDK (@emithook/sdk).

What's remaining

The short list of surfaces still on the roadmap:

• Python & Go SDKs Roadmap — the TypeScript SDK ships today; Python and Go are next. Until then, generate a client from the OpenAPI spec (the interim codegen path).
• Terraform provider Roadmap — declarative management of endpoints/destinations/keys.
• A second AWS region Roadmap — for multi-region / DR beyond the current single managed region.
• Optional runtime CF→SQS failover Roadmap — a configurable runtime failover of the ingest buffer from Cloudflare Queues to SQS. Off by default (it re-introduces a cross-cloud dependency on the accept path); SQS already ships as a selectable deploy-time buffer.
• The inbound-email front door Roadmap — inbound email ships today on SES; whether the platform default moves to Cloudflare Email Workers (with SES retained for residency) is an open positioning decision. The path is behind the InboundEmailPort seam, so it's an adapter choice, not a rewrite.

Surface status at a glance

Surface	Status
HTTPS ingest, signing, retries, DLQ, logs, archive, replay, Pull API	Available
Console, management API, Send API (/v1/send)	Available
CLI, MCP server, TypeScript SDK	Available
Queue destinations & ingestion (all brokers)	Available
Application fan-out (/v1/app/{id}/event), consumer portal	Available
Inbound email + agent inbox	Available
Python / Go SDKs, Terraform provider	Roadmap
Second AWS region, optional runtime CF→SQS failover	Roadmap

Changelog: github.com/emithook/emithook/releases.