I built a tool that documents your entire Bubble app automatically — backend + frontend (ERD, API specs, workflow docs)

Showcase
1

Hey Bubblers :waving_hand:

After 5+ years of building on Bubble, I kept hitting the same wall: the apps grew way past the point where anyone could hold them in their head — dozens of data types, hundreds of backend workflows, API Connector calls everywhere, and pages full of conditionals nobody remembers writing.

When you need to explain all that to someone else — a new team member, a client, an external developer, an investor doing due diligence — there’s no export button. You end up screenshotting the editor for days.

So I built Relis. It connects to your app with viewer-only collaborator access and automatically extracts your full architecture:

  • Data structure — data types, fields, relationships, option sets, privacy rules
  • API Connector — every connection with auth, headers, params, request/response
  • Backend workflows — API workflows, scheduled events, DB triggers, with full condition/action sequences (+ a screenshot of every workflow)
  • App settings — domain, languages, environment info
  • Frontend — pages, reusable elements, element trees, custom states, conditionals, and UI workflows

The backend side comes out as 9 developer-standard documents: ERD (Mermaid), DDL script (PostgreSQL/MySQL), table specification, data dictionary, API spec, backend workflow docs, enum/constants, full markdown exports, and workflow screenshots. The frontend comes as a structured overview for each page.

A few things I want to be upfront about:

  • It’s read-only. Viewer access only — it extracts structure and logic, never your database records or user data. Revoke access anytime.
  • The free scan gives you a complexity report (how many types, workflows, API calls, and pages you actually have). Full document generation is paid.
  • I’m the founder — happy to answer anything about how it works under the hood.

Use cases so far: onboarding developers onto an existing app, agencies producing documentation deliverables for clients, and architecture audits.

Would love feedback from people with big apps — the gnarlier the backend, the better the test. :folded_hands:

→ relis.dev

2

This is a really good idea! Well :white_check_mark:.

What’s the cost associated with this if I was to run this and grab the extract?

3

Thanks Tim, appreciate it! :folded_hands:

The scan itself is completely free — it shows what’s actually in your app (data types, fields, backend workflows, API calls, pages) plus a complexity score.

If you then want the full extract, the price is calculated from that same scan: a small base fee plus per-field / per-API-call / per-workflow-step rates, so the cost scales with your app’s actual size — a small MVP costs a fraction of what a big production app does. You see the exact quote upfront before paying anything, and there’s a 50% launch discount active right now.

So the easiest way to answer “what would it cost for my app” is to run the free scan — it doubles as your exact quote.

4

Very cool idea. And may be a good starting point as well for people using claude-code/codex to transition their app off bubble

5

image
image640×268 9.31 KB

This is not the URL for all bubble apps, Specifically for dedicated

6

@anewinn That’s exactly the workflow it’s built for. The full markdown export is structured so agents like Claude Code / Codex can consume it directly — every backend workflow with its triggers, conditions and step sequences, plus the frontend structure (pages, reusables, conditionals, custom states) so the agent knows what each screen is supposed to do, not just what the data looks like. The gap I kept running into was never “can AI write the code” — it was “does the AI know what to build.”

@Nakita Good catch, thank you — you’re right. The App ID input currently assumes the standard bubble.io editor URL format, and I haven’t tested against a Dedicated instance yet (they run on their own domains). I’d genuinely like to support it — if you’re on Dedicated and open to it, could you DM me what your editor URL format looks like? Happy to prioritize this.