What Briks does

#From a description to a live site

You write what you need in ordinary words: who it is for, what it offers, how it should feel and which pages it needs. Briks takes it from there in six stages, and you can follow each one in the project's conversation.

1. Plan. Briks reads your description and asks which pages you want. Unless you switch it off, it also asks about anything your words leave open, such as whether you take bookings or show prices. You can answer in a minute, or press Decide for me and take its recommendations.
2. Design. It settles colours, type, spacing and pictures for your kind of business. If you show it a site you like, it reads its layout, spacing, type, motion and header menu and follows it, without copying its words.
3. Build. It writes the pages and the code behind them. A website gets its sections, menu and forms. An app or a dashboard gets its screens and, when it needs to keep information, a database of its own. If building usually takes more credits than you have, it waits once planned, with the plan kept, until you choose Resume building.
4. Check. Before publishing, Briks checks the contrast of text against its background in the code. After the first publish it checks contrast again on the live page at desktop and phone width, with at most one repair, and makes sure every page you chose is in the menu. An app's code is also read for common security mistakes, such as a key left in a file.
5. Host. The site runs on Briks, and hosting is part of your plan. A live site stays online whatever your credit balance.
6. Publish. The first publish is a preview at its own address, such as larder-lane.briks.live, kept out of search engines. When you are happy, Publish to production runs a launch check and makes it a public site in full.

After that, you change the site by typing in the same conversation: 'make the opening hours easier to find', or 'add a page for wholesale customers'. Every build and every change is saved as a version, so you can undo, redo or go back to an earlier one if a change was not what you meant.

#Three kinds of project

When you start a project you choose what you are making. The choice shapes how Briks plans it, which questions it asks and how the screens are laid out.

Websites and web apps start with questions about pages and anything unclear. Dashboards skip those questions and are built straight from the description, and they have no look or hero to choose. The web apps and dashboards page covers the differences in detail.

#What you need to start

• An email address you can open. Your account is confirmed by a link sent to it, and you cannot sign in until you click it.
• A description of the business or idea. Ten characters is the minimum, but the best first versions come from a paragraph that says who it is for and where, what it offers, how it should feel and which pages it needs. See writing a good brief.
• Optional: a site you like. One address, plus screenshots of whole pages or single sections. See build from a site you like.
• Optional: your brand. An accent colour, light or dark, and the fonts for headlines and text, if they are already fixed. Leave anything else to Briks.
• Optional: your own photos and videos. You can add them later from the media library or attach them to a message in the conversation.
• No card. A new account starts with 50 free credits, which is what a first build holds while it runs. A Free workspace's first site is built in full even when it needs more than that.
• Later, for your own domain: a domain you own and the Starter plan or above. Every plan, Free included, gets a briks.live address.

#A typical first hour

Here is how the first hour usually goes for someone starting from nothing. The only timing the studio itself promises is that the first version takes a few minutes; the rest depends on how long you spend reading and deciding.

#What Briks does not do yet

Some things people ask for are not built yet. Knowing them before you write your brief saves a build spent on something that cannot work.

• Subscriptions through every processor. Plans that renew need Stripe, Paddle, Polar or Lemon Squeezy, set up under Settings, Payments. PayPal, Mollie, Razorpay, Creem and Dodo Payments take one-time payments only for now. See Sign-in and payments.
• Exporting form entries. Messages sent through your site's forms are kept in the studio, where the latest 100 are shown, and emailed to you once the site is in production. There is no export button. If you need them somewhere else, a webhook can send each new entry to another service as it arrives.
• Email from your own domain. Site email, when you switch it on, sends from an address at emails.briks.live, not from your own domain.
• An exact price before you build. A job holds a set amount while it runs (50 credits for a new site) and is charged for the work it took, which can be lower or higher. When a build usually takes more credits than you have, the studio says so before it starts, with an estimate from builds like it. See credits and plans.
• A free custom domain. Your own domain starts on the Starter plan.
• A public API or an MCP server. You build and manage sites in the dashboard, or from Telegram. The only key for your own tools is a project's analytics key on a paid plan, which reads its visitor figures. See analytics.
• Syncing with any service other than GitHub. On a paid plan, a site's files can be kept in step with a GitHub repository and downloaded from the studio. See GitHub sync.
• A full check of every build. The check at four screen sizes for layout, overlap and links is something you switch on. It does not run on every build unless you ask.
• Reselling Briks under your own name. There is no white-label option today. The small Built with Briks badge always shows on Free sites. On a paid plan it is off unless you switch it on.
• AI agents on the Free plan. AI agents that look after a site for you come with paid plans, from Starter.

#How these docs are organised

The docs follow the order most people work in, from a first account to a team running several sites.

If you are new, read Create your account, take the tour of the dashboard, then follow Your first site with your own business in mind. Anything that sounds like jargon is explained in Words we use.