A clever prompt is not a product. Real apps need auth, secrets, run history, rate limits, observability, and durable state. Building all that yourself is weeks of plumbing.

Floom is the missing layer.

Six production-grade layers, one config. Ingest a spec, get MCP + HTTP + CLI + Web + Share, each with auth, secrets, runs, and a renderer. Deploy is docker run.

Open source, Docker-first.

MIT licensed, single binary, 30-second self-host. No lock-in, no SaaS dependency for your critical path. Run it on a $5 VPS, a laptop, or a cluster.

WHAT'S IN THE BOX

Six shipped layers. Zero glue code.

Each one has a real endpoint, a real renderer, and a real test. No placeholders.

Ingest

Point at OpenAPI URL or GitHub repo. Floom resolves operations, infers schemas, builds the app.

POST /api/ingest
{ "url": "https://x.com/api.json" }

Runtime

Sandboxed execution. Sync + job queue for >30s runs. Per-app concurrency caps. Retries + DLQ.

POST /api/run
→ { run_id, status: "success" }

Secrets

Encrypted at rest, scoped per app + per creator. Never in logs. Rotatable without redeploy.

# .floom/secrets.yaml
OPENAI_KEY: $env://OPENAI_KEY

Memory

Per-session state. KV, file-scoped, app-scoped. Survives container restart. TTL-aware.

session.set("last_doc", doc_id)
session.get("last_doc")

Runs

Every call logged: inputs, outputs, duration, client, status. Full replay + diff across runs.

GET /api/run/:id
→ { inputs, outputs, duration_ms }

Renderer

Auto-generated form from schema. Custom renderers for bespoke UIs. Mobile-first by default.

renderer: "auto" // or "./my-ui.tsx"

FEATURED APPS

Try one running right now.

See all 22 →

opendraft

WhatsApp-first email drafting assistant · Gemini 3 Pro

2,143 runs‡

Try

openpaper

Turn any PDF into a conversation · long-context retrieval

8,912 runs‡

Try

bouncer

Independent quality audits for code, video, copy

1,087 runs‡

Try

openslides

Generate pitch decks from a bullet-point outline

643 runs‡

Try

uuid

Zero-config UUID generator · v4 / v7 / v1 · the demo above

35,606 runs‡

Try

CLAUDE DESKTOP · 3 LINES

Add any Floom app to Claude.

Paste into Claude Desktop → Settings → Developer → Edit Config. That's it.

1{
2  "mcpServers": {
3    "floom": {
4      "command": "npx",
5      "args": ["-y", "mcp-remote", "https://floom.dev/mcp"],
6      "env": { "FLOOM_API_KEY": "fk_live_..." }
7    }
8  }
9}

Claude Desktop

5-line JSON config

Cursor / Zed

Same config, different path

ChatGPT (GPT Actions)

Point at /openapi.json

SELF-HOST

Run it on your own box.

Single image. Single command. No extra services required for a development instance.

~/floom

$ docker run -p 3010:3010 -p 3051:3051 ghcr.io/floomhq/floom:latest

[floom v0.4.2] bootstrapping...

✓ runtime started (pid 1, port 3010)

✓ mcp gateway listening (port 3051)

✓ sqlite migrations applied (schema v14)

✓ 14 apps registered [opendraft, openpaper, bouncer, uuid, ...]

✓ secret store initialized (age-encrypted)

ready. http://localhost:3010

$ _

Need customization?

Fork the repo, mount your own apps directory, override the renderer. Full guide.

Read the self-host guide →

Need scale?

Helm chart for K8s, Postgres replacement for SQLite, Redis for the job queue. Cloud tier handles it.

Floom Cloud →

FROM CREATORS‡

What weekend-project builders say.

Floom lets me ship an agent to Claude in five minutes. I haven't looked at a backend since.‡

@federicodeponte

Building in Hamburg

I had a JSON API on a Friday, MCP + web form by Saturday. Weekend-project energy, production discipline.‡

@jannik-ships‡

SignalDash

The self-host story is the whole thing. One docker run, no SaaS in my critical path, still get the Claude integration for free.‡

@gourav-codes‡

OpenPaper

‡ Example placements; actual testimonials will replace these at launch.

ROADMAP · COMING NEXT

Shipping loud.

Six Cloud-tier additions in the next two quarters. Vote on what lands first.

Stripe Connect monetization Workspaces + teams Composio connections App memory (persistent) Schedules + cron Custom domains

Vote on what ships next →

BUILT IN HAMBURG

By @federicodeponte + 3 contributors.

Floom grew out of shipping seven weekend projects and realizing the same plumbing kept getting rewritten. Open source from day one; MIT licensed because lock-in is a bug.

GitHub ★ 127‡ Discord X / @floomhq team@floom.dev

github.com/floomhq/floom

floomhq / floom public

The protocol + runtime for agentic work. MIT licensed.

127‡

STARS

22‡

FORKS

14‡

ISSUES

TypeScript 84% ● Shell 11% ● Dockerfile 5%

MOBILE · 375px · anon · all 13 sections stack

floom.dev

floom

v0.4 · open source

Production infrastructure for AI apps that do real work.

The protocol + runtime for agentic work.

Vibe-coding speed. Production-grade safety.

No API yet? Browse 22 apps →

WORKS WITH

Claude·ChatGPT·Cursor·Zed·+ 12 more

127‡

APPS

48,391‡

RUNS

312‡

CREATORS

SHIPPED BY

@federicodeponte · @buildingopen · @floomhq‡

ARCHITECTURE

One spec. Five surfaces.

YOUR SPEC

FLOOM RUNTIME

MCP

Claude / Cursor

HTTP

POST /run

CLI

floom run

Web

Embeddable form

Shareable form

Public permalink renderer

LIVE DEMO

Try it with a real app.

INPUTuuid

version count

OUTPUT11ms

// success
{ "uuids": [
"bff0a7bf-..."
] }

WHY FLOOM

Three problems, one runtime.

AI apps are toys without infra.

Prompt ≠ product. Real apps need auth, secrets, runs, rate limits.

Floom is the missing layer.

Six layers, one config. Ingest → MCP + HTTP + CLI + Web + Share.

Open source, Docker-first.

MIT licensed. Single binary. 30-second self-host.

WHAT'S IN THE BOX

Six shipped layers.

Ingest

OpenAPI → app.

Runtime

Sandboxed, queued.

Secrets

Encrypted at rest.

Memory

Per-session KV.

Runs

Every call logged.

Renderer

Auto form from schema.

FEATURED APPS

Try one now.

CLAUDE · 3 LINES

Add any app to Claude.

{
 "mcpServers": {
  "floom": {
   "command": "npx",
   "args": ["-y", "mcp-remote",
      "https://floom.dev/mcp"]
  }}}

SELF-HOST

Run it on your own box.

$ docker run -p 3010:3010
ghcr.io/floomhq/floom

[floom v0.4.2] booting...

✓ runtime · port 3010

✓ mcp · port 3051

✓ 14 apps registered

FROM CREATORS‡

Weekend-project energy.

Ship an agent to Claude in five minutes.‡

@federicodeponte

Hamburg

ROADMAP

Shipping loud.

Stripe Connect Workspaces Composio App memory Schedules Custom domains

Vote on what ships next →

BUILT IN HAMBURG

By @federicodeponte + 3.

GitHub ★ 127‡ Discord X

Open source, MIT licensed.

Docs · Changelog · Status · Imprint · Privacy · Terms

‡ Illustrative placeholders; real metrics at launch.

LOGGED-INDESKTOP · 1280px · creator with published apps (Store-first; Studio is secondary)

floom.dev

floom

Store Studio Me

3 apps published · 2,143 runs this week‡

Welcome back, Federico.

Browse the Store, or jump back into Studio.

Browse 22 apps Open Studio →

YOUR APPS‡

Full landing sections (Why · Layers · Apps · MCP · Self-host · Roadmap · Built-by · Footer) render identically below the fold for both anon and logged-in users. Logged-in dashboard tiles above replace the Proof row.

Built in Hamburg · Docs · MIT licensed · v0.4.2

SPEC NOTES · v16 LANDING REDESIGN

13 sections (vs. 4 in v15 landing): Hero → Proof → Architecture → Demo → Why → Layers → Apps → MCP → Self-host → Testimonials → Roadmap → Built-by → Footer.
Hero is 3 layers: H1 benefit ("Production infrastructure for AI apps that do real work.") + Sub positioning ("The protocol + runtime for agentic work.") + Green accent ("Vibe-coding speed. Production-grade safety."). Locked per MEMORY.md · Floom Positioning 2026-04-18.
Illustrative metrics marked with ‡: every fabricated number (127 apps, 48,391 runs, GitHub stars, per-app run counts, testimonial handles) is footnoted. Footer discloses the convention. Live counters will replace these at launch from /api/hub + /api/metrics.
Architecture diagram (Section 3): typographic SVG. Spec pill → runtime node → five clickable surface tiles (MCP / HTTP / CLI / Web / Share), each anchoring to /docs#<surface>.
Inline demo (Section 4): two-column runner with input form (left) + output JSON (right). Renders the same uuid app the v2 shipped code uses. 11ms round-trip shown.
Layers grid (Section 6): 6 cards, each with title + 1-line description + mini code snippet. Six layers match memory/project_floom_layers.md.
Featured apps expanded from 3 → 5: opendraft, openpaper, bouncer, openslides, uuid (matches v2 shipped roster).
MCP snippet (Section 8): dark-themed code block with hand-highlighted JSON + Copy button. Three follow-up tiles: Claude Desktop, Cursor/Zed, ChatGPT (GPT Actions).
Self-host boot output: docker run + simulated startup logs (✓ runtime · ✓ mcp · ✓ 14 apps). "Need to customize?" / "Need scale?" cards follow.
Testimonials section: kept per task spec. ALL THREE clearly marked ‡ with footer disclosure. Using real handles only for @federicodeponte; the other two are @jannik-ships‡ and @gourav-codes‡ (illustrative derivatives of real peers). This can be commented out at Federico's call.
Roadmap peek (Section 11): 6 pills for Cloud-tier v1.1+ items (Stripe Connect, Workspaces, Composio, App memory, Schedules, Custom domains). CTA to GitHub Issues.
Built-by / community (Section 12): Hamburg credit, 4 social links, mini GitHub card with stars/forks/issues + language bar. MIT licensed line woven into prose, not robotic.
Footer expanded to 5 columns (Product / Resources / Community / Legal + brand block). Status badge + version number on the baseline.
Mobile frame (right column): all 13 sections stack cleanly at 375px. Hero shrinks to 34px serif, integration row becomes dot-separated text, demo becomes vertical, layers grid becomes 2-column.
Logged-in variant: Proof row is replaced by "Your apps" dashboard tile (3 user-owned apps with 7d run counts). Same chrome, same nav (Store first, Studio second per v16 creator-nav-first rule).
Anti-patterns avoided: no em dashes; no purple (green #059669 is the single accent, Store and Studio share it); no fabricated logos; no "Used by 10,000+ teams"; no "You got this" CTA copy; no fake testimonials without ‡ marker.

Landing · /

Production infrastructurefor AI apps that do real work.

One spec. Five surfaces.

Try it with a real app.

Three problems one runtime solves.

AI apps are toys without infra.

Floom is the missing layer.

Open source, Docker-first.

Six shipped layers. Zero glue code.

Ingest

Runtime

Secrets

Memory

Runs

Renderer

Try one running right now.

Add any Floom app to Claude.

Run it on your own box.

Need customization?

Need scale?

What weekend-project builders say.

Shipping loud.

By @federicodeponte + 3 contributors.

Production infrastructure for AI apps that do real work.

One spec. Five surfaces.

Try it with a real app.

Three problems, one runtime.

AI apps are toys without infra.

Floom is the missing layer.

Open source, Docker-first.

Six shipped layers.

Ingest

Runtime

Secrets

Memory

Runs

Renderer

Try one now.

Add any app to Claude.

Run it on your own box.

Weekend-project energy.

Shipping loud.

By @federicodeponte + 3.

Welcome back, Federico.

Production infrastructure
for AI apps that do real work.