BubblevsFerraFerra is the Bubble alternative for people who don't want to build software
Bubble is where you build the app. Ferra is where the work gets tracked.
See how Ferra compares to Bubble
| Functionalities | Ferra | Bubble |
|---|---|---|
| Getting started | Part of what this tool is for. The rows come first: paste, upload, or forward. | Possible, with a step you do yourself. Design the pages, define data types, wire the workflows. |
| Filling the rows | Part of what this tool is for. Reads your files and forwarded emails, writes the rows. | Possible, with a step you do yourself. The page's list stays empty until records exist. |
| Adding a field later | Part of what this tool is for. Add the column, describe it. It fills from the same sources. | Possible, with a step you do yourself. Add it to the data type, then update bound pages. |
| Designing the interface | A different tool's job. No canvas, no element tree: describe what you are tracking. | Part of what this tool is for. A real visual editor: layout, components, styling. |
| Shipping something to real users | A different tool's job. No launch step. There is nothing to launch. | Part of what this tool is for. Sign-ups, screens you designed on purpose, a Deploy button. |
| Asking a question | Part of what this tool is for. Ask in plain English, the summary points at its rows. | Possible, with a step you do yourself. Build the page, or a search with the right constraints. |
| Dashboards and reports | Part of what this tool is for. Ask for the report and it lands on the dashboard, keeping up as rows change. | Possible, with a step you do yourself. A chart is an element you place and bind to a search. |
| Automation | Part of what this tool is for. “Email me when an invoice goes past due”, the sentence is the rule. | Part of what this tool is for. Workflows are the heart of the editor: event, conditions, actions. |
| Changing your mind later | Part of what this tool is for. Another sentence, and the rows you already have come with it. | Possible, with a step you do yourself. An edit to the design, and to everything bound to it. |
The app exists before the data does
In Bubble you design pages, define data types, wire workflows: the first version is a shell.
Ferra starts from the rows and builds the table and dashboard around them.
No workflows to wire
A Bubble rule is a workflow you assemble: event, conditions, actions. A Ferra rule is a sentence: watch this table, email me when an invoice goes past due.
Nothing to launch
A Bubble project deploys because other people will use it. A Ferra workspace has no launch, your data lives there from the first hour.
Changing your mind is cheap
Renaming a field or splitting a table is an edit to an app you built. In Ferra it is another sentence.
Frequently asked questions
What people ask before they move a table across: about Ferra, about Bubble, and about which of the two fits the work you actually have.
Only if you wanted the result, not the app. Ferra gives you tables, dashboard and answers, no app in the middle.
No: no canvas, no element tree. Describe what you are tracking and adjust it the same way.
For the common ones, yes: a new row, a changed value or a missed date, then an email or an update.
Tables with your rows, a dashboard reading them, and an assistant that answers from both.
Files you upload, emails you forward, connected apps, and public web sources.