Made for
Building it from scratch: Anyone willing to own every part of the stack
madeso: Business owners and operations people building with AI
Build it yourself · Compare
Every option below is good at something. The difference is how many of the ten jobs behind business software are left for you, or your AI, to build, connect and look after.
Claude, Grok or ChatGPT can write a lot of code quickly. Built from scratch, every piece around that code is yours: choosing it, connecting it, securing it and keeping it running.
Building it from scratch: Anyone willing to own every part of the stack
madeso: Business owners and operations people building with AI
Building it from scratch: Whatever database you choose and design
madeso: The madeso data engine. Say what you track and how it links
Building it from scratch: A sign-in service you add, and rules you write
madeso: Built in: sign-in, two-step codes, invites and roles
Building it from scratch: Code for each tool, plus storing its keys
madeso: API connections, an encrypted key vault and functions
Building it from scratch: A host you set up and a deploy you run
madeso: Already hosted. Changes are mostly setup in the data engine, with nothing to deploy
Building it from scratch: Build, host and supervise your own
madeso: Built in: agents that update records, send emails and run on a schedule
Building it from scratch: You
madeso: We do
You're a developer, or you have one, and you want total control of every line, or you're building a product to sell rather than a system to run your business.
You'd rather spend the week on the part that's unique to your business than on logins, hosting and servers.
Somewhere to keep everything
Yours to doBuilding it from scratch: Choose a database and design it, or have Claude do it and check the result.
madeso: The data engine is already there. Say what you track and how things link, and it's set up.
Letting the right people in
Yours to doBuilding it from scratch: Pick a sign-in service, wire it into every screen and handle the forgotten passwords.
madeso: Logins, two-step sign-in and team invites come with every workspace.
Deciding who sees what
Yours to doBuilding it from scratch: Write the access rules and test that every screen and query follows them.
madeso: Roles decide which apps and which data each person can open. Set them once and every app follows them.
Connecting your other tools
Yours to doBuilding it from scratch: Register with each tool, then store and refresh its tokens.
madeso: API connections come built in. People link their accounts once, keys stay in an encrypted vault, and functions can talk to any tool with an API.
Keeping passwords and keys safe
Yours to doBuilding it from scratch: Keep keys out of the code, the chat and the browser.
madeso: Keys for your other tools live in an encrypted vault, apart from your app's screens.
Putting it online
Yours to doBuilding it from scratch: Choose a host, set up the domain and learn the deploy steps.
madeso: It's already hosted. There's no server, domain or app store to manage.
Work that runs on its own
Yours to doBuilding it from scratch: Set up somewhere for scheduled work to run, and watch it.
madeso: Functions and schedules run for you, and public functions can take webhooks from other tools.
Everyone seeing the latest
Yours to doBuilding it from scratch: Build live updates and decide what happens when the signal drops.
madeso: Changes show on every device straight away, and apps keep working when the signal drops.
When a change breaks something
Yours to doBuilding it from scratch: Test every change yourself before it reaches your team.
madeso: There's far less to break. Building on madeso is mostly setting up the data engine: what you track, how things link and who can see what. The database, server, logins, connections and hosting are the engine's job, so you don't have a whole stack of your own code that can go wrong.
Keeping it running
Yours to doBuilding it from scratch: Security updates, backups and outages are yours, for as long as the app runs.
madeso: We run the servers and the database, watch them, and keep the engine up to date. A fix to the engine reaches every app at once.
Most businesses run on a handful of subscriptions, joined by built-in integrations, automation tools like Zapier or Make, and someone copying between them.
Off-the-shelf software: As many businesses as possible
madeso: Your business, the way it actually works
Off-the-shelf software: Split across each app
madeso: One place, shared by every app
Off-the-shelf software: A login and permission settings in every app
madeso: One login and one set of roles across every app
Off-the-shelf software: Built-in integrations where they exist, automation tools where they don't
madeso: Apps share one set of data, so there's less to connect
Off-the-shelf software: Hosted by each vendor. Changes wait for their roadmap
madeso: Hosted. Ask for a change in plain English
Off-the-shelf software: Whatever each app offers, inside that app only
madeso: Built in, working across all your apps' data
Off-the-shelf software: Each vendor, plus whoever owns the automations
madeso: We do
A tool already fits how you work, or it's a specialist job like accounting or payroll that your accountant needs in a particular package. Keep those.
Your team keeps spreadsheets beside the software, or copies between apps every day.
Somewhere to keep everything
Partly doneOff-the-shelf software: Each app stores its own part, and the same customer lives in several places.
madeso: The data engine is already there. Say what you track and how things link, and it's set up.
Letting the right people in
Done for youOff-the-shelf software: Done per app, so your team juggles a login for each one.
madeso: Logins, two-step sign-in and team invites come with every workspace.
Deciding who sees what
Partly doneOff-the-shelf software: Set separately in each app, if the app offers the control you need.
madeso: Roles decide which apps and which data each person can open. Set them once and every app follows them.
Connecting your other tools
Partly doneOff-the-shelf software: Built-in integrations cover popular cases. The rest needs an automation tool or copying.
madeso: API connections come built in. People link their accounts once, keys stay in an encrypted vault, and functions can talk to any tool with an API.
Keeping passwords and keys safe
Done for youOff-the-shelf software: Each vendor looks after its own. Your automation tool holds the keys between them.
madeso: Keys for your other tools live in an encrypted vault, apart from your app's screens.
Putting it online
Done for youOff-the-shelf software: Each vendor hosts its app.
madeso: It's already hosted. There's no server, domain or app store to manage.
Work that runs on its own
Partly doneOff-the-shelf software: Whatever each app's features allow, plus automations you build and maintain.
madeso: Functions and schedules run for you, and public functions can take webhooks from other tools.
Everyone seeing the latest
Partly doneOff-the-shelf software: Live inside each app, but not across them.
madeso: Changes show on every device straight away, and apps keep working when the signal drops.
When a change breaks something
Partly doneOff-the-shelf software: Vendor updates are tested by them. Automations can quietly break when a field changes.
madeso: There's far less to break. Building on madeso is mostly setting up the data engine: what you track, how things link and who can see what. The database, server, logins, connections and hosting are the engine's job, so you don't have a whole stack of your own code that can go wrong.
Keeping it running
Done for youOff-the-shelf software: Each vendor runs its own app. Someone still owns the joins.
madeso: We run the servers and the database, watch them, and keep the engine up to date. A fix to the engine reaches every app at once.
Supabase is a strong backend for developers: a Postgres database with live updates, sign-in, file storage, edge functions and scheduled jobs. You, or your AI, still write the app in code and wire those parts together.
Supabase: Developers writing an app in code
madeso: Business owners and operations people building with AI
Supabase: A Postgres database you design
madeso: The madeso data engine. Say what you track and how it links
Supabase: Supabase Auth, plus row-level security rules you write
madeso: Built in: sign-in, two-step codes, invites and roles
Supabase: Edge functions you write for each tool
madeso: API connections, an encrypted key vault and functions
Supabase: Hosts the backend. Your screens usually go on another host
madeso: Already hosted, screens included
Supabase: Supabase runs the backend. Your app code is yours to maintain
madeso: We run the lot
You have developers, want full control of the code and a standard Postgres database, or you're building a product for lots of outside users.
You want the whole system working for your team without wiring a backend to a front end and a host.
Somewhere to keep everything
Partly doneSupabase: A full Postgres database is ready. Designing the tables is yours.
madeso: The data engine is already there. Say what you track and how things link, and it's set up.
Letting the right people in
Partly doneSupabase: Supabase Auth handles sign-in, including Google. You wire it into your screens.
madeso: Logins, two-step sign-in and team invites come with every workspace.
Deciding who sees what
Yours to doSupabase: You write and test row-level security policies.
madeso: Roles decide which apps and which data each person can open. Set them once and every app follows them.
Connecting your other tools
Yours to doSupabase: Write edge functions for each tool, and handle each tool's tokens.
madeso: API connections come built in. People link their accounts once, keys stay in an encrypted vault, and functions can talk to any tool with an API.
Keeping passwords and keys safe
Partly doneSupabase: Functions can hold secrets. Keeping keys out of the browser is on you.
madeso: Keys for your other tools live in an encrypted vault, apart from your app's screens.
Putting it online
Partly doneSupabase: The backend is hosted. Your screens need hosting and deploying too.
madeso: It's already hosted. There's no server, domain or app store to manage.
Work that runs on its own
Partly doneSupabase: Cron and queues exist. You write and deploy the work.
madeso: Functions and schedules run for you, and public functions can take webhooks from other tools.
Everyone seeing the latest
Partly doneSupabase: Realtime is built in. You build the screens that use it.
madeso: Changes show on every device straight away, and apps keep working when the signal drops.
When a change breaks something
Yours to doSupabase: You test and deploy each change.
madeso: There's far less to break. Building on madeso is mostly setting up the data engine: what you track, how things link and who can see what. The database, server, logins, connections and hosting are the engine's job, so you don't have a whole stack of your own code that can go wrong.
Keeping it running
Partly doneSupabase: Supabase runs the backend. Your code and its dependencies are yours.
madeso: We run the servers and the database, watch them, and keep the engine up to date. A fix to the engine reaches every app at once.
Based on the public Supabase docs, November 2026.
Convex is a reactive backend for developers: a database with live updates, TypeScript functions, scheduling and file storage, with official plugins for AI coding tools. Your app's code and screens are still yours to write and host.
Convex: Developers writing an app in TypeScript
madeso: Business owners and operations people building with AI
Convex: A database with a schema you define in code
madeso: The madeso data engine. Say what you track and how it links
Convex: Convex Auth or a partner like Clerk, plus checks you write
madeso: Built in: sign-in, two-step codes, invites and roles
Convex: Actions you write to call each tool
madeso: API connections, an encrypted key vault and functions
Convex: Hosts the backend. Its docs point to hosts like Vercel or Netlify for the screens
madeso: Already hosted, screens included
Convex: An Agent component for developers to build agents in code
madeso: Built in: agents that update records, send emails and run on a schedule
Convex: Convex runs the backend. Your app code is yours to maintain
madeso: We run the lot
You have TypeScript developers who want a live, code-first backend and full control over the app around it.
You want live, shared data without writing and deploying the app around it.
Somewhere to keep everything
Partly doneConvex: The database is ready. The schema and queries are code you write.
madeso: The data engine is already there. Say what you track and how things link, and it's set up.
Letting the right people in
Partly doneConvex: Convex Auth or a partner like Clerk. You wire it in.
madeso: Logins, two-step sign-in and team invites come with every workspace.
Deciding who sees what
Yours to doConvex: You write the access checks in your functions.
madeso: Roles decide which apps and which data each person can open. Set them once and every app follows them.
Connecting your other tools
Yours to doConvex: Write actions for each tool and handle its tokens.
madeso: API connections come built in. People link their accounts once, keys stay in an encrypted vault, and functions can talk to any tool with an API.
Keeping passwords and keys safe
Partly doneConvex: Environment variables hold keys. Using them safely is on you.
madeso: Keys for your other tools live in an encrypted vault, apart from your app's screens.
Putting it online
Partly doneConvex: The backend is hosted. Screens go on another host.
madeso: It's already hosted. There's no server, domain or app store to manage.
Work that runs on its own
Partly doneConvex: Scheduled functions and crons exist. You write them.
madeso: Functions and schedules run for you, and public functions can take webhooks from other tools.
Everyone seeing the latest
Partly doneConvex: Live by default. You build the screens.
madeso: Changes show on every device straight away, and apps keep working when the signal drops.
When a change breaks something
Yours to doConvex: You test and deploy each change.
madeso: There's far less to break. Building on madeso is mostly setting up the data engine: what you track, how things link and who can see what. The database, server, logins, connections and hosting are the engine's job, so you don't have a whole stack of your own code that can go wrong.
Keeping it running
Partly doneConvex: Convex runs the backend. Your code is yours.
madeso: We run the servers and the database, watch them, and keep the engine up to date. A fix to the engine reaches every app at once.
Based on the public Convex docs, November 2026.
Firebase is Google's app platform for developers: a live database, sign-in including Google, cloud functions, hosting and security rules, with Gemini built into its tools. You still write the app and its rules.
Firebase: Developers building web and mobile apps
madeso: Business owners and operations people building with AI
Firebase: Firestore, designed by you
madeso: The madeso data engine. Say what you track and how it links
Firebase: Firebase Authentication, plus security rules you write
madeso: Built in: sign-in, two-step codes, invites and roles
Firebase: Cloud functions you write for each tool
madeso: API connections, an encrypted key vault and functions
Firebase: Hosting is included. You build and deploy each change
madeso: Already hosted. Changes are mostly setup in the data engine, with nothing to deploy
Firebase: Google runs the infrastructure. Your app is yours to maintain
madeso: We run the lot
You're building a consumer app, especially on mobile, with developers who know Google's tools.
You're building internal systems for your own business and don't want to write security rules and deploy pipelines.
Somewhere to keep everything
Partly doneFirebase: Firestore is ready. Designing the data is yours.
madeso: The data engine is already there. Say what you track and how things link, and it's set up.
Letting the right people in
Partly doneFirebase: Sign-in, including Google, is provided. You wire it in.
madeso: Logins, two-step sign-in and team invites come with every workspace.
Deciding who sees what
Yours to doFirebase: You write and test security rules.
madeso: Roles decide which apps and which data each person can open. Set them once and every app follows them.
Connecting your other tools
Yours to doFirebase: Cloud functions you write, plus each tool's tokens.
madeso: API connections come built in. People link their accounts once, keys stay in an encrypted vault, and functions can talk to any tool with an API.
Keeping passwords and keys safe
Partly doneFirebase: Tools exist for keys. Setting them up safely is yours.
madeso: Keys for your other tools live in an encrypted vault, apart from your app's screens.
Putting it online
Partly doneFirebase: Hosting is included. You run the deploys.
madeso: It's already hosted. There's no server, domain or app store to manage.
Work that runs on its own
Partly doneFirebase: Scheduled functions exist. You write them.
madeso: Functions and schedules run for you, and public functions can take webhooks from other tools.
Everyone seeing the latest
Partly doneFirebase: Firestore syncs live. You build the screens.
madeso: Changes show on every device straight away, and apps keep working when the signal drops.
When a change breaks something
Yours to doFirebase: You test and deploy each change.
madeso: There's far less to break. Building on madeso is mostly setting up the data engine: what you track, how things link and who can see what. The database, server, logins, connections and hosting are the engine's job, so you don't have a whole stack of your own code that can go wrong.
Keeping it running
Partly doneFirebase: Google runs the platform. Your code is yours.
madeso: We run the servers and the database, watch them, and keep the engine up to date. A fix to the engine reaches every app at once.
Based on the public Firebase docs, November 2026.
Netlify is a platform for building and deploying web apps: hosting, preview links, functions (including scheduled and background ones), forms, a database option, sign-in through Netlify Identity, and AI agents that can change your code.
Netlify: Teams shipping websites and web apps from code
madeso: Business owners and operations people building with AI
Netlify: Netlify Database or Blobs, designed by you
madeso: The madeso data engine. Say what you track and how it links
Netlify: Netlify Identity, with roles you set up in rules and code
madeso: Built in: sign-in, two-step codes, invites and roles
Netlify: Functions you write for each tool
madeso: API connections, an encrypted key vault and functions
Netlify: Excellent hosting, with a preview link for every change
madeso: Already hosted. Changes are mostly setup in the data engine, with nothing to deploy
Netlify: Netlify runs the hosting. Your app code is yours
madeso: We run the lot
You're shipping a public website or a web app from code, and great hosting and previews matter most.
The hard part is the business data, logins and permissions behind the screens, not the hosting.
Somewhere to keep everything
Partly doneNetlify: A database option is ready. Designing it is yours.
madeso: The data engine is already there. Say what you track and how things link, and it's set up.
Letting the right people in
Partly doneNetlify: Netlify Identity handles sign-in, including Google and invite-only. You wire it in.
madeso: Logins, two-step sign-in and team invites come with every workspace.
Deciding who sees what
Partly doneNetlify: Identity roles exist. You decide and code what each role can see.
madeso: Roles decide which apps and which data each person can open. Set them once and every app follows them.
Connecting your other tools
Yours to doNetlify: Write functions for each tool and handle its tokens.
madeso: API connections come built in. People link their accounts once, keys stay in an encrypted vault, and functions can talk to any tool with an API.
Keeping passwords and keys safe
Partly doneNetlify: Environment variables hold keys. Using them safely is on you.
madeso: Keys for your other tools live in an encrypted vault, apart from your app's screens.
Putting it online
Done for youNetlify: Hosting and deploys are Netlify's core strength.
madeso: It's already hosted. There's no server, domain or app store to manage.
Work that runs on its own
Partly doneNetlify: Scheduled and background functions exist. You write them.
madeso: Functions and schedules run for you, and public functions can take webhooks from other tools.
Everyone seeing the latest
Yours to doNetlify: You build live updates into your app.
madeso: Changes show on every device straight away, and apps keep working when the signal drops.
When a change breaks something
Partly doneNetlify: Preview links let you check a change first. Testing it is still yours.
madeso: There's far less to break. Building on madeso is mostly setting up the data engine: what you track, how things link and who can see what. The database, server, logins, connections and hosting are the engine's job, so you don't have a whole stack of your own code that can go wrong.
Keeping it running
Partly doneNetlify: Netlify runs the hosting. Your code is yours.
madeso: We run the servers and the database, watch them, and keep the engine up to date. A fix to the engine reaches every app at once.
Based on the public Netlify docs, November 2026.
No-code builders let you make apps by clicking and dragging. Bubble includes a database, user accounts, workflows, plugins and hosting, plus an AI app generator. Glide makes apps from your data, and Airtable adds screens and automations to a spreadsheet-style database.
No-code builders: People who want to build by clicking in an editor
madeso: Business owners and operations people who'd rather describe it in plain English
No-code builders: Inside the builder's own database or tables
madeso: The madeso data engine, shared by every app
No-code builders: Built into most, with privacy settings you configure
madeso: Built in: sign-in, two-step codes, invites and roles
No-code builders: Plugins and API connectors
madeso: API connections, an encrypted key vault and functions
No-code builders: Hosted. Changes are made by hand in the editor
madeso: Hosted. Changes are made by AI from plain English
No-code builders: The vendor
madeso: We do
You enjoy building visually, the app fits the builder's blocks, and you're happy for one person to own the editor.
You'd rather describe what you need than learn an editor, and you want every app sharing one set of data.
Somewhere to keep everything
Partly doneNo-code builders: A database is included. You design it in the editor.
madeso: The data engine is already there. Say what you track and how things link, and it's set up.
Letting the right people in
Done for youNo-code builders: User accounts are built into most.
madeso: Logins, two-step sign-in and team invites come with every workspace.
Deciding who sees what
Partly doneNo-code builders: Privacy settings exist. You configure each one.
madeso: Roles decide which apps and which data each person can open. Set them once and every app follows them.
Connecting your other tools
Partly doneNo-code builders: Plugins and API connectors. You set each one up.
madeso: API connections come built in. People link their accounts once, keys stay in an encrypted vault, and functions can talk to any tool with an API.
Keeping passwords and keys safe
Partly doneNo-code builders: Keys live in the connector settings.
madeso: Keys for your other tools live in an encrypted vault, apart from your app's screens.
Putting it online
Done for youNo-code builders: Hosted by the vendor.
madeso: It's already hosted. There's no server, domain or app store to manage.
Work that runs on its own
Partly doneNo-code builders: Workflows and automations you build in the editor.
madeso: Functions and schedules run for you, and public functions can take webhooks from other tools.
Everyone seeing the latest
Partly doneNo-code builders: Depends on the builder.
madeso: Changes show on every device straight away, and apps keep working when the signal drops.
When a change breaks something
Partly doneNo-code builders: Bubble separates a test version from the live app. Checking changes is yours.
madeso: There's far less to break. Building on madeso is mostly setting up the data engine: what you track, how things link and who can see what. The database, server, logins, connections and hosting are the engine's job, so you don't have a whole stack of your own code that can go wrong.
Keeping it running
Done for youNo-code builders: The vendor runs it.
madeso: We run the servers and the database, watch them, and keep the engine up to date. A fix to the engine reaches every app at once.
Based on the public Bubble manual, November 2026.
A good developer or agency can build exactly what you ask for. The trade-off is time, cost and that every change after launch goes back through them.
Hiring a developer or agency: Businesses with a clear spec and a budget
madeso: Business owners and operations people building with AI, with us there to help
Hiring a developer or agency: Wherever they choose
madeso: The madeso data engine, in your workspace
Hiring a developer or agency: Built by them
madeso: Built in: sign-in, two-step codes, invites and roles
Hiring a developer or agency: Built by them
madeso: API connections, an encrypted key vault and functions
Hiring a developer or agency: Hosted where they set it up. Changes go through them
madeso: Hosted. You or your AI make changes in plain English
Hiring a developer or agency: Them, under a support agreement, or you
madeso: We do
The system is large, unusual or regulated, and you want a team accountable for building it to a written spec.
You want to change things yourself next week. And if you'd still like it built for you, we'll build your first app free.
Somewhere to keep everything
Their jobHiring a developer or agency: They build it. Changing it later goes back through them.
madeso: The data engine is already there. Say what you track and how things link, and it's set up.
Letting the right people in
Their jobHiring a developer or agency: They build it. Changing it later goes back through them.
madeso: Logins, two-step sign-in and team invites come with every workspace.
Deciding who sees what
Their jobHiring a developer or agency: They build it. Changing it later goes back through them.
madeso: Roles decide which apps and which data each person can open. Set them once and every app follows them.
Connecting your other tools
Their jobHiring a developer or agency: They build it. Changing it later goes back through them.
madeso: API connections come built in. People link their accounts once, keys stay in an encrypted vault, and functions can talk to any tool with an API.
Keeping passwords and keys safe
Their jobHiring a developer or agency: They build it. Changing it later goes back through them.
madeso: Keys for your other tools live in an encrypted vault, apart from your app's screens.
Putting it online
Their jobHiring a developer or agency: They build it. Changing it later goes back through them.
madeso: It's already hosted. There's no server, domain or app store to manage.
Work that runs on its own
Their jobHiring a developer or agency: They build it. Changing it later goes back through them.
madeso: Functions and schedules run for you, and public functions can take webhooks from other tools.
Everyone seeing the latest
Their jobHiring a developer or agency: They build it. Changing it later goes back through them.
madeso: Changes show on every device straight away, and apps keep working when the signal drops.
When a change breaks something
Their jobHiring a developer or agency: They test their changes. New changes wait for their time.
madeso: There's far less to break. Building on madeso is mostly setting up the data engine: what you track, how things link and who can see what. The database, server, logins, connections and hosting are the engine's job, so you don't have a whole stack of your own code that can go wrong.
Keeping it running
Their jobHiring a developer or agency: Under a support agreement, or it comes back to you.
madeso: We run the servers and the database, watch them, and keep the engine up to date. A fix to the engine reaches every app at once.
Get started today
Get started and build your first app yourself. Or book a call and we'll build it with you, free, then you take it from there.