AI app builder
Build a web app with AI, with its own database
Describe what your app should keep and show. Briks builds the pages, the database behind them, the forms that save and the search, then reads the code for security and hosts the result.
- Its own database, created with the build
- Forms, scheduled jobs and webhooks
- Code read for security before it publishes
| Event | Date | Published |
|---|---|---|
| 12 Apr | ||
| 20 Apr | ||
| 25 Apr |
Rename an event or switch one on.
What is on at Oak Hall
- 12 AprSpring craft fairDetails and times
- 20 AprRepair caféDetails and times
Live, built from 2 published records
What a web app means in Briks
A website shows the same pages to everyone. A web app keeps data and works with it. In Briks that comes down to these parts, built together from your description.
Records in a database
Things you keep a list of, such as recipes, events, jobs or suppliers, live as records in the app's own database. You add and edit them in the studio.
Pages built from the records
Each record can have its own page, and listing pages sort and filter them. Pages are built ahead of time, so every record is a real page search engines can find.
Forms that save
Contact and enquiry forms keep every entry, and a form can save what visitors send as a record in your database.
Search
Visitors can search your records, through routes that belong to your app and run beside its pages.
Scheduled jobs and webhooks
Run a task on a timetable, and tell your other tools when the site is published, a form arrives or a record changes.
Dashboards, when you need numbers
A screen of figures, charts and tables for your team is a dashboard, its own kind of project.
AI dashboard builder
What you can build with the AI app builder today
Each example uses only what Briks does now. Where part of an idea is not available yet, the card says so.
- Records and pages
A recipe or menu collection
Every dish is a record with its own page. Your team edits the records in the Database tab, and the live site is published again with the change.
- Records and a feed
A news section or blog
Posts kept as records, newest first, each with its own page, and a feed for readers who follow along.
- Records and pages
An events listing or class timetable
Events or classes as records, each with its date and its own page, in the order you ask for. A place can be paid for once, through your own payment processor.
- Records, search and forms
A jobs board or directory with search
Listings as records with a page each, a search that runs through the app's own routes, and applications that arrive through a form.
- Forms and webhooks
Request and enquiry forms
Booking requests, quotes or applications, kept in the studio and emailed to you in production, with a webhook to pass each one on to another tool.
- Accounts and payments
Member sign-up and paid places
Visitors sign up with email and password, or with Google and seven more providers on your own keys, and pay once for a place, a download or a service through your own processor.
- Accounts and payments
Memberships that renew
Members subscribe to a plan that renews each month or year, with an optional free trial, through your own Stripe, Paddle, Polar or Lemon Squeezy account. Pages can be kept for subscribers.
- Payments, on request
Shipping and delivery charges
Ask for shipping and Briks builds it into your app with your own payment account: posted orders, with the delivery charges you set.
- Dashboard
A dashboard for your team
A screen of key figures, charts and tables, built from your description. Its figures are the ones you give.
How dashboards are built
Your app's own database, with records you can edit
In the studio, the Database tab works like the table here: every collection, every record, ready to change.
When a build stores data, the database comes with it. An Owner or Admin can also create one by hand in the Database tab. Each collection, such as recipes, events or suppliers, is a table of records you can view, add to and edit.
When records change, the live site is published again so the pages built from them stay current: at once the first time, then at most once every five minutes, however many edits you make. Each change can also be sent to your other tools as a record.changed webhook.
Your records are yours to take. On a paid plan, download a collection as CSV, or everything as JSON in a zip, up to 50,000 records per collection, and switch on nightly copies, each kept for 30 days.
- Created with the build, or by hand
- View, add and edit in the Database tab
- Downloads as CSV or JSON on paid plans, up to 50,000 records per collection
- Nightly copies kept for 30 days on paid plans, when switched on
| Bread | Price | On sale |
|---|---|---|
| Country sourdough | ||
| Seeded rye | ||
| Cardamom bun |
Forms that keep every entry
There is no form service to sign up for. What people send through your app's forms is kept for you.
Entries are kept in the studio for each site, where the latest 100 are shown. Once the site is in production, each new entry is also emailed to you. Entries sent to the briks.live preview are kept but not emailed, so testing never fills your inbox.
To pass entries to another tool, add a webhook for form.received, and it is told about each entry as it arrives.
Form entries cannot be exported yet. When you need to keep and export what visitors send, ask for a form that saves to your database instead: on a paid plan, those records download like any others.
FormsScheduled jobs and webhooks for your app
Connect your app to the rest of your tools without running a server of your own.
A scheduled job calls one of your app's own routes, or an address you give, at the times you set, and every run is kept in a history. Jobs run whether or not the site is published.
A webhook tells another tool the moment something happens: the site is published, a form is received or a record changes. Each delivery is signed so the receiver can check it came from your app, and one that fails is tried up to five times: at once, then after about 30 seconds, 2 minutes, 8 minutes and 32 minutes.
Your app can also send email under its own name from an address on emails.briks.live, once you switch email on: 300 emails a month on Free, 2,000 on Starter, 5,000 on Pro, 15,000 on Studio and 50,000 on Agency, shared by all your sites.
- 1 scheduled job and 1 webhook per project on Free, 5 of each on Starter, 10 on Pro, 25 on Studio and 50 on Agency
- Events: site.published, form.received, record.changed
- A test delivery whenever you ask for one
Scheduled jobs
- Send the weekly digestMondays at 08:00, calls /api/digestLast run done
- Close past eventsEvery day at 02:30, calls /api/tidyLast run done
Webhook to hooks.example.com
- form.receivedDelivered on the first try
A failed delivery is tried again after about 30 seconds, 2 minutes, 8 minutes and 32 minutes.
Your app's code, open to you
Nothing is hidden behind the builder. Every file written for your app is there to read.
Browse every file written for your app in the studio. Anyone with edit rights can change a file by hand, and on a paid plan you can download the code as a zip whenever you like.
The zip holds the code written for your app, not the shared parts every Briks site runs on, so it needs work to run anywhere else. On paid plans those files can also be kept in a GitHub repository, in step both ways. Your records are yours either way: on a paid plan, download them as CSV or JSON.
Prefer plain words? Ask for the change in the studio chat instead. It is built, published and saved as a version you can undo.
Your site's codeexport default function Order() {
return (
<Section pad="lg">
<OrderForm day="saturday" />A security read before your app publishes
Apps that keep data need care. Before publishing, Briks reads the code written for your app for the mistakes that most often leak data.
The read looks for keys and passwords written into files, routes that change data with no limit on how often, data taken in without being checked, database queries built by joining strings, HTML set from raw text, and pages or routes that call another address. What it finds goes back to the builder to fix.
Secrets your app needs are set in the studio and kept out of its files. Colour contrast is checked too, in the code and on the live page, as on every Briks site.
On paid plans, the Security agent keeps checking after launch: the code after every publish and the live site every Monday, with each finding in plain words and every fix waiting for your approval.
The Security agent- Keys and passwords written into files
- Routes that change data with no limitFound in the route that takes applications, and fixed: a limit was added.
- Data taken in without being checked
- Database queries built from strings
- HTML set from raw text
- Pages or routes that call another address
Read complete. Nothing left to fix.
What apps cannot do yet
Better to know now than after you build. None of these is available today.
- Not yet
Calls to outside services
Pages and routes cannot call other services' addresses yet. Webhooks and scheduled jobs are the way to connect other tools today.
- Not yet
Exporting form entries
Form entries stay in the studio and your inbox. Records in your database can be downloaded on a paid plan.
- Not yet
Email from your own domain
Site email sends from an address on emails.briks.live under your site's name, not from your domain.
- Not yet
Data from other tools in dashboards
Dashboards keep their records in their own database, starting with sample records, and save from their forms. They do not read your other databases or tools yet.
AI dashboard builder - Not yet
A command line or a public API
Everything is done in the studio: building, changes, records, jobs and webhooks.
What it costs to build an app
Apps use the same credits and plans as websites.
A hold is set aside while the work runs. Each job is then charged for the work it took: what it does not use comes back, anything past the hold is drawn from your balance, and a request that fails is not charged.
Free
$0to start
- 50 credits at sign-up, then 5 a day that build up to 25
- 1 site
- A briks.live address
- 500 MB storage
Starter
$16a month
or $160 a year, 2 months free
- 175 credits a month
- 1 site
- Your own domain
- 5 GB storage
Pro
$29a month
or $290 a year, 2 months free
- 400 credits a month
- 3 sites
- 3 of your own domains
- 10 GB storage
Studio
$79a month
or $790 a year, 2 months free
- 1,200 credits a month
- 10 sites
- 10 of your own domains
- 25 GB storage
Agency
$199a month
or $1,990 a year, 2 months free
- 3,000 credits a month
- 30 sites
- 30 of your own domains
- 100 GB storage
The Free plan's 50 credits are given once; there is no daily top-up. Paid plans are bought online at checkout, monthly or yearly. Compare every plan
Questions about the AI app builder
Can I build a web app with AI without coding?
Yes. Describe what the app should keep and show, and Briks builds the pages, the database and the forms. Changes are asked for in plain words, and if you do code, you can edit the files yourself.
Does my app get its own database?
Yes, when it stores data. The database is created with the build, or by an Owner or Admin in the Database tab. You can view and edit its records, and download them on a paid plan.
Can people sign in to my app?
Yes. Ask for accounts and your app gets sign-up and sign-in with email and password, with confirmation and reset emails sent from the site. Google, Apple, Microsoft, GitHub, X, Facebook, LinkedIn and Discord switch on in Project settings with your own app keys, on every plan.
Can my app take payments?
Yes, one-time payments through your own Stripe, PayPal, Mollie, Razorpay, Paddle, Lemon Squeezy, Polar, Creem or Dodo Payments account, connected in Project settings, and subscriptions that renew monthly or yearly through Stripe, Paddle, Polar or Lemon Squeezy. Briks takes no fee on your sales. Need shipping? Ask for it and Briks builds it into your app with your own payment account.
How do I connect my app to other tools?
With webhooks and scheduled jobs. Webhooks tell another tool when the site is published, a form is received or a record changes, and scheduled jobs call a route or an address on a timetable. Pages and routes cannot call outside services yet.
Can I export my app's data?
Yes, on a paid plan: records in your database download as CSV or JSON, up to 50,000 per collection. Form entries cannot be exported yet; they are kept in the studio and emailed to you in production.
Is my app checked for security?
Yes. Before publishing, the code written for your app is read for keys left in files, routes with no limit, unchecked input, SQL built from strings and calls to outside addresses, and what it finds is sent back to be fixed. On paid plans, the Security agent checks it again after every publish.
Can I download my app's code?
Yes, on a paid plan, as a zip whenever you like. It holds the code written for your app but not the shared parts every Briks site uses, so it does not run on its own. On paid plans those files can also be kept in a GitHub repository, in step both ways.
What is the difference between an app and a dashboard?
An app here is a site that keeps records and works with them: pages, forms and search. A dashboard is a screen of figures, charts and tables for a team, built from its own kit with no motion or decoration.
How much does it cost to build an app?
The same as a website. A new build holds 50 credits and a change holds 5, and each is charged for the work it took. You start free with 50 credits at sign-up, then 5 a day that build up to 25, and paid plans start at $16 a month, bought online at checkout.
What will your app keep track of?
Describe it in a sentence. Start with 50 free credits, no card needed.