# Build brief — a focused alternative to Bubble

> **Verdict:** Partly, if you narrow it · **Buildability:** 49/100 · **Category:** No Code Apps
> **Source:** https://www.canitbevibecoded.com/bubble
> Independent editorial assessment from Can It Be Vibe Coded? Not affiliated with, endorsed by, or derived from Bubble. Verify current pricing and capabilities before acting.

## Context

**Bubble** — No-code platform for building custom web apps with workflows and data. It currently costs $32/mo.

A specific Bubble app is often vibecodable now; rebuilding Bubble's editor, workflow engine, plugin ecosystem, hosting, and scaling layer is not.

This brief describes a focused, single-operator replacement for the part of Bubble that is genuinely reproducible. It is deliberately narrower than the product it replaces, and it says so in writing. Build the useful core; do not pretend to have rebuilt the rest.

## What you are building

Rebuild the target app directly in code with CRUD, auth, workflows, and hosting rather than cloning Bubble as a platform.

- Build a focused single-user workflow with real persistence, search, and export.
- A responsive interface with real empty, loading, success, and error states.

## Requirements

### Functional

- Web framework.
- Database.
- Auth.
- Hosting.
- Product-specific integrations.

### Data and integrations

- Payment/email APIs.

Each of these needs a real account, credential, or quota. Set them up before writing feature code.

### Non-functional

- Accessibility: semantic markup, labelled controls, visible focus, and reduced-motion support.
- Security: server-side secrets, validated input, and no credentials in the client bundle.
- Reliability: retries with backoff on external calls, and a clear failure state when a provider is down.
- Portability: the operator can export their data and leave without losing it.

## Implementation brief

Build me the app I currently run on Bubble, as plain code I own. Requirements:

- First ask me for: the 3-5 core screens, the data types with their fields,
  and the single workflow that matters most. Rebuild that app, not Bubble.
- Stack: Node + Express + better-sqlite3, server-rendered EJS templates plus
  htmx for interactivity. No SPA framework, no build step.
- CRUD for each data type: list page with search and filters, detail page,
  create and edit forms with validation.
- Workflows become plain functions: a form submit updates rows, sends email
  via Resend (key in .env), redirects. Scheduled workflows become node-cron
  jobs in the same process.
- Auth only if people other than me log in: email+password sessions with
  bcrypt and a session cookie, no roles unless I named them. If it is just
  me, skip auth and bind to localhost.
- File uploads go to uploads/, images resized with sharp.
- One SQLite file plus a nightly CSV dump of every table, data never trapped.
- Out of scope: a visual editor, a plugin system, anything platform-shaped.
  The deliverable is one app that deploys with node server.js on a $5 VPS.
- README: deploy steps and how to add a field later, the code is the editor
  now.

## Delivery standard

- Inspect the repository first, then write a short implementation plan before writing code.
- Deliver the smallest complete end-to-end workflow first; every primary control must work against persisted data.
- Use real validation and storage; never substitute fake dashboards, decorative controls, hard-coded success states, or mock integrations.
- Include responsive layouts plus genuine empty, loading, success, validation, and failure states.
- Keep secrets server-side in environment variables, provide .env.example, and never commit credentials or user data.
- Add structured logs around every external call and return actionable errors without leaking sensitive details.
- Write unit tests for the core logic and one automated test of the main user journey.
- Finish with a README covering setup, architecture, data location, backups, tests, deployment, and known limitations.

## Acceptance criteria

- [ ] A clean install starts the app using only the README and .env.example.
- [ ] The primary journey works from first visit through saved result, reload, edit, export, and deletion where applicable.
- [ ] Invalid input, missing configuration, provider failure, and an empty database each have a usable state.
- [ ] The interface works at 390px and 1440px, is keyboard navigable, and shows visible focus on every control.
- [ ] Tests, type checking, linting, and a production build all pass with no ignored failures.
- [ ] No part of the interface implies a live integration, security guarantee, or scale capability that was not actually built and verified.

## Non-goals

Do not build these, and do not claim to have replaced them:

- Visual editor.
- Workflow builder.
- Plugin marketplace.
- Hosting/scaling.
- The last 20 percent is sync, migration fidelity, speed, and edge cases.
- Connectors, OAuth flows, and vendor API changes require constant upkeep.

## What you still own after launch

- Secure credentials, rotate secrets, and handle provider rate limits.
- Run migrations, backups, restores, and dependency updates.
- Test the critical journey after every model, API, or hosting change.
- Monitor failures and fix the edge cases a first prompt will miss.
- Maintain every third-party integration as APIs and OAuth rules change.

## Risk

**Operational risk.** The code is achievable; dependable data, integrations, and ongoing operations are the real cost.

Editorial confidence in this assessment: high. No independent one-shot implementation is linked yet.

## Prior art

Working open-source software you can read, fork, or borrow from before starting:

- [Appsmith](https://github.com/appsmithorg/appsmith) — Open-source low-code builder for internal tools; partial prior art for visual app building

---

Generated by [Can It Be Vibe Coded?](https://www.canitbevibecoded.com) · Full report: https://www.canitbevibecoded.com/bubble