The code is yours
On every planDownloads on paid plans
- Read it
- The File Explorer shows the files written for your site, as the live version holds them.
- Edit it
- People with edit rights can change files by hand and publish them, with no AI and no credits. A save that breaks a publish rule is held back, and nothing goes live if the build fails.
- Download it
- On a paid plan, anyone in the workspace can download the live version, or an earlier one, as a zip.
- What it leaves out
- The download holds your site's own files. It leaves out the shared parts every Briks site runs on, settings files and keys, so it does not run on its own.
GitHub sync
Paid plans
- Connect
- Owners and Admins connect a repository and a branch to a project.
- Briks to GitHub
- Every version that goes live becomes a commit on your branch.
- GitHub to Briks
- A push to your branch is checked against the same publish rules, built and published, with no AI.
- Conflicts
- When both sides changed the same file, Briks puts its version on a
briks-syncbranch for you to merge. It never force-pushes. - What goes there
- Your site's own files only, so the repository does not run on its own. Settings files, database changes and keys are never part of it.
Each site's database
On every planDownloads on paid plans
- Its own database
- A site that stores data gets its own database, made in the European Union by default, the first time a build needs one.
- In the studio
- View, search, sort, add and edit records collection by collection, with views of the site's accounts, orders and subscriptions.
- Downloads
- On a paid plan, download every collection as JSON, or one collection as CSV.
- Changing its shape
- Ask for a new field or collection in plain words. Changes only ever add, Briks takes a restore point before applying them, and a change that would lose data stops the publish.
- Going back
- Owners and Admins can take the database back to an earlier moment or a restore point. On a paid plan, nightly copies are kept for 30 days.
Scheduled tasks, webhooks and deploy hooks
On every planLimits by plan
- Scheduled tasks
- Call a route on your site, or any secure web address, on a schedule in your own time zone. Each run is logged for 30 days.
- Webhooks
- Signed messages in the Standard Webhooks format to any secure address when the site is published, a form entry arrives or a record is changed in the studio:
site.published,form.receivedandrecord.changed. A failed delivery is tried again for about 45 minutes. - Deploy hooks
- A private address that publishes the site again when another tool calls it, with no AI.
| Plan | Scheduled tasks | Webhooks | Calls a day |
|---|---|---|---|
| Free | 1 | 1 | 2,000 |
| Starter | 5 | 5 | 5,000 |
| Pro | 10 | 10 | 10,000 |
| Studio | 25 | 25 | 50,000 |
| Agency | 50 | 50 | 100,000 |
Each project has its own allowance. Calls a day count scheduled runs and webhook deliveries together.
Secrets
On every plan
- Where they live
- Keys your server code needs are saved straight to the published site, encrypted. Briks keeps only their names, and no one can read a value back.
- Adding them
- Once the site is published, Editors, Admins and Owners add up to 100 for each project, one at a time or from a .env file.
- Using them
- Your server code reads each key by its name. A key never reaches a visitor's browser, and one written into a file stops the publish.
Payments with your own account
Every plan, Free included
- Your own processor
- Stripe, PayPal, Mollie, Razorpay, Paddle, Lemon Squeezy, Polar, Creem or Dodo Payments, one at a time, with your own account and keys. The money goes to you, and Briks takes no fee.
- Checkout and subscriptions
- One-off checkout works with each of them. Subscriptions, with an optional free trial, work with Stripe, Paddle, Polar and Lemon Squeezy.
- Verified
- Every payment report is verified before an order counts, and orders and subscriptions are kept in the site's own database.
- Keys
- Owners and Admins save them. Each is tried first, then kept with the published site.
Sign-in for your visitors
On every plan
- By default
- Email and password, with email confirmation and password reset.
- Providers
- Add Google, Apple, Microsoft, GitHub, X, Facebook, LinkedIn or Discord with your own keys.
- Members only
- Keep pages and records for signed-in members, or for subscribers.
Ask for anything, within a few fixed rules
On every plan
- Your request comes first
- Ask in plain words for your own server code, another service connected with your key, or a payment flow of your own. A fix Briks makes afterwards never undoes what you asked for.
- Your call, with the risk named
- A few payment rules bend only when you ask in so many words, such as letting the buyer choose the amount. The build keeps it and tells you the risk.
- Other websites
- Allow up to 10 websites you trust in the project's settings, so your site can load their scripts, send them data or show their pages.
- Rules that never bend
- A key written into a file, a secret key read in the browser, and code that reads Briks's own keys are refused, whoever asks.
Checks on every publish
On every plan
- The publish rules
- Every build, change, hand edit and GitHub push is checked against them. A change that breaks one is not published, and the live site stays as it was.
- A security read
- Code Briks writes is read for the mistakes that most often leak data, and what is found goes back to be fixed before it publishes.
- A launch check
- Moving to production checks for placeholder text, pages without a title or description, links that lead nowhere and a missing not-found page.
Logs
On every plan
- Builds
- Every build, change and publish, with the steps each went through.
- Requests
- The last 24 hours of requests and errors from your site's own server code.
- Tasks and webhooks
- Each scheduled run and webhook delivery, kept for 30 days.
Not available today
- An API or MCP server for building and managing sites from your own tools.
- Importing an existing repository into Briks.