← All posts

What you can build with Basable

product guide

The first post said what Basable is and what it is not. This one is about what you can actually do with it: what you can build, how you work on it, and how far you can take it once it is live.

Start with a sentence

You open a project and describe what you want. “A booking page for my hairdresser, with a form that emails me.” “An internal dashboard over our order data.” “A REST API for a mobile app, backed by Postgres.”

The assistant does not guess at the choices that are expensive to undo. When your description leaves the framework, the database or the login method open, it asks, with a few concrete options to pick from, and then gets on with it. You can also pick which AI model does the work.

What you can build

Everything on Basable ships as a container, which keeps the list of what you can build long:

Internal tools, customer portals, a prototype you want in front of real users this week: if it runs in a container and speaks HTTP, it runs here.

Start from nothing, or from what you have

A new project can start empty, in a fresh repository Basable creates in your GitHub organisation. Or you connect a repository you already have and let the assistant work on that. Either way the code lives on your GitHub, the build runs in your own GitHub Actions, and there is no export step, because nothing is ever held back.

Preview first, then live

Every project has two environments. Work lands on the dev branch and deploys to a preview with its own address, which you can send to a colleague or a customer before anything is public. When you are happy, Merge & Deploy merges to main and the live environment follows.

A preview that nobody touches for thirty minutes goes to sleep and stops costing anything. The next push wakes it.

Keep changing it

Iterating is the same conversation. Ask for a new page, a different layout, an extra field in the form. Each change is committed, built, deployed to the preview, and waits there for you to look at it.

You do not have to go through the assistant. Clone the repository, change a file by hand, push, and the platform deploys what you pushed. Mix the two as you like: let the assistant scaffold a feature and polish the details yourself.

Put it on your own domain

Every environment gets a secure address on basable.com out of the box. When the project is ready for its real name, you can put your own domain on it, with TLS certificates handled for you. The domains guide explains the options, including keeping your DNS exactly where it is and adding two records.

When you want to look under the hood

Basable is built so that developers never hit a wall:

Where it runs

Each project runs in its own isolated environment, with its own resource limits and network rules, on a sandboxed runtime that keeps it apart from everyone else’s at the kernel level. The servers are in the EU.

Every new organisation gets a month free for each environment. After that you pay for the capacity you reserve, by the second, with no base fee. The pricing page has the exact rates.

Try it

Basable is in alpha, so expect some rough edges (the first post is honest about which). The fastest way to see what it can do is to describe something you have been meaning to build. Get started with just your email address. While we are in alpha, creating an organisation takes an alpha password: ask us for one and we will send it to you.