--- title: "Common questions about Briks | Briks" url: https://briks.dev/docs/faq description: "Short, straight answers about Briks: what it is, what it costs, the free plan, domains, your data, teams and clients, and what is coming next." last_updated: 2026-10-08 --- # Common questions about Briks The questions people ask us most, answered in a few sentences each. Every answer links to the page with the full story. Prices and limits are as of 20 October 2026. 7 minute read Checked against the studio on 8 October 2026 ## The basics ### What is Briks? Briks is a studio that turns a written description of a business into a working website, web app or dashboard. It plans the pages, designs them, writes the words and the code, checks the result and publishes it. It then hosts the site and gives you analytics, forms and more. See [What Briks does](https://briks.dev/docs/introduction). ### Who is it for? Business owners, freelancers and agencies who want a real site without hiring a developer or learning a site builder. It suits a bakery, a physiotherapy clinic, a photographer, a trades firm, a small software company, or an agency running sites for clients. ### Do I need to know how to code? No. You describe what you want in plain words, and you ask for changes the same way. If you do write code, you can browse and edit the files Briks wrote for your site, and download them on a paid plan. See [Your site's code](https://briks.dev/docs/code). ### How long does a first site take? It depends on the number of pages and on whether you've asked Briks to stop for your approval along the way. You watch it happen: the studio shows each step as it builds and how long it has been running. See [Watching a build](https://briks.dev/docs/watching-a-build). ### Will my site work on phones? Yes. Sites are built for phones, tablets and computers, and the preview lets you switch between widths so you can see each one before you publish. ## Building ### What should I write in the brief? Who the business is, who it's for, the pages you want, the one thing a visitor should do (call, book, enquire), and real facts such as prices, hours and the area you serve. See [Writing a good brief](https://briks.dev/docs/writing-a-brief) for worked examples. ### Can I show Briks a site I like? Yes, one site per project plus screenshots. Briks reads how it's put together (layout, spacing, type and motion) and builds yours in that spirit with your own words and pictures. It doesn't copy it. See [Build from a site you like](https://briks.dev/docs/build-from-sites-you-like). ### Can I use my own photos and logo? Yes. Upload them to the media library and attach them to your brief or to a change. Replacing a picture on your site with one of yours uses no credits. See [Pictures](https://briks.dev/docs/pictures) and [Media library](https://briks.dev/docs/media-library). ### How do I change something after it's built? Type the change in the project's conversation in plain words, the way you'd tell a designer. Each change sets aside 5 credits and publishes when it's done. If you don't like the result, undo it. On a paid plan you can also click a page in the [Visual Editor](https://briks.dev/docs/visual-editor) and change words and pictures by hand, with no credits. See [Making changes](https://briks.dev/docs/making-changes). ## Credits and plans ### What is a credit? Credits pay for the work Briks does for you: building, changing, checking and your agents' runs. A job sets credits aside before it starts (50 for a new site, 5 for a change, 5 for a check) and is charged for the work it took. What it doesn't use comes back. A request that fails isn't charged. See [Credits and plans](https://briks.dev/docs/credits-and-plans). ### What does the free plan include? 50 credits once when you sign up, 1 site on a briks.live address, 500 MB of storage, and 300 site emails a month. It is for you alone: custom domains and AI agents start on Starter, and inviting people on Pro. Your first site is built in full even if it takes more than those credits. See the [pricing page](https://briks.dev/pricing). ### How do I get a paid plan? Open **Billing** in the studio, choose a plan, monthly or yearly, and pay at checkout. Starter is $16 a month, Pro $29, Studio $79 and Agency $199, or pay for a year and get 2 months free: $160, $290, $790 and $1,990 a year. Each comes with monthly credits, your own domain and AI agents. Starter is for one site; Pro and above add more sites and room for your team. See [Billing](https://briks.dev/docs/billing). ### Can I buy extra credits? Not on their own: credits come with a plan, every month on a paid one. To get more, move up a plan, and the extra credits for the rest of the month arrive at once. Write to hello@briks.dev if you need more than the largest plan gives. ### Can I see what a build will cost before it starts? Each job is charged for the work it took, so there is no fixed price. When a build, or a change that adds pages, usually takes more credits than you have, the studio says so first with an estimate from builds like it. A build that needs more once planned waits, with its plan kept, until you choose **Resume building**. See [Credits and plans](https://briks.dev/docs/credits-and-plans). ## Publishing and domains ### Is my site public as soon as it's built? It is published to a preview address, such as yourname.briks.live, which anyone with the link can open. Search engines are asked to leave it alone, and form messages aren't emailed. When you're ready, **Publish to production** runs a launch check and makes it a real public site. See [Preview and production](https://briks.dev/docs/preview-and-production). ### Can I use my own domain? Yes, from the Starter plan. You add three records at your registrar, and Briks verifies the domain and sets up its security certificate for you, renewing it automatically. See [Connect your domain](https://briks.dev/docs/custom-domains). ### Will search engines find my site? Once it's in production, yes: every published site has page titles, descriptions and a sitemap. New sites take time to appear, and you can help by adding yours to the search engines' own tools. See [Search engines](https://briks.dev/docs/search-engines). ## Your data ### Who owns my site? Your content is yours: the words you write, the files you upload, your brand, and your site's words and records. The words, designs and code Briks writes for your site are yours to use. Pictures the studio draws for you may also be used on other Briks sites; the photos you upload are used only on yours. The [Terms](https://briks.dev/terms) set this out in full. ### Can I download my code? Yes, on a paid plan, as a zip of the files Briks wrote for your site. It doesn't include the shared building blocks the studio provides, so it won't run on its own. See [Your site's code](https://briks.dev/docs/code). ### Can I export my form entries? Not yet. Entries are kept in the studio, and the latest 100 are shown. To send each one somewhere else as it arrives, such as a spreadsheet tool, use a webhook for new form messages. See [Forms](https://briks.dev/docs/forms) and [Webhooks](https://briks.dev/docs/webhooks). ### How are my visitors counted? Without cookies. A visitor is told apart by a code that changes every day, and their network address isn't kept. See [Analytics](https://briks.dev/docs/analytics). ### Where is my data kept, and how long for? The [Privacy Policy](https://briks.dev/privacy) explains what we keep, why, for how long and where it is processed. You can delete your account from **Profile**, under **Danger zone**. ### Is there a data processing agreement for my visitors' data? Yes. The [Terms](https://briks.dev/terms#processing) include data processing terms: for your sites' visitors you are the controller and Briks processes their data for you, as the GDPR asks. They also give an entry you can copy into your own records. ## Teams and clients ### Can my team work on the same site? Yes, from the Pro plan. Invite people to your workspace as an Owner, Admin, Editor or Viewer. Pro has room for 3 people, Studio 10 and Agency 25, you included, with no seat fees. Free and Starter are for the owner alone. See [Members and roles](https://briks.dev/docs/members-and-roles). ### How do I hand a site over to a client? Build it in a workspace for that client, then invite them as an Owner, which works on any plan. You can then stay on as an Admin or leave. See [Handing a site to a client](https://briks.dev/docs/handing-over-to-a-client). ### Can I put my own brand on Briks for my clients? Not yet. A white-label version, with your own brand in place of Briks, isn't available. ## What's coming ### Can I sell online or let visitors sign in? Yes, on every plan. A site that needs accounts gets email and password sign-in, and Google, Apple, Microsoft, GitHub, X, Facebook, LinkedIn and Discord switch on with your own keys under **Settings**, **Sign-in**. Payments go through your own processor under **Settings**, **Payments**, once or as plans that renew monthly or yearly through Stripe, Paddle, Polar or Lemon Squeezy, and Briks takes no fee. Shipping is built into your site when you ask, with your own payment account. See [Sign-in and payments](https://briks.dev/docs/sign-in-and-payments). ### What are the AI agents? Agents that look after a site for you: answering visitors, following up leads, writing articles, posting to social accounts, checking security and reporting each week, with a Team lead to plan their week. They ask you before anything goes out, in the studio, by email or on Telegram. They come with paid plans, from Starter. See [Hire AI agents](https://briks.dev/docs/ai-agents) and [Approvals and budgets](https://briks.dev/docs/agent-approvals). ### Is there an API or an MCP server? Not for building or managing sites: you do that in the studio, or from [Telegram](https://briks.dev/docs/telegram). On a paid plan, a project's analytics key lets your own tools read its visitor figures. See [Analytics](https://briks.dev/docs/analytics). ### What else is on the way? GitHub sync is here: on a paid plan, a site's files can be kept in a GitHub repository in step both ways. See [GitHub sync](https://briks.dev/docs/github). ### How do I get help? Start with [Troubleshooting](https://briks.dev/docs/troubleshooting). If that doesn't cover it, write to hello@briks.dev with your project's name and what you expected to see. ## Read next - [Getting started **What Briks does** Briks plans, designs, builds, checks, hosts and publishes websites, web apps and dashboards from a plain description. What it does, and what it cannot do yet.](https://briks.dev/docs/introduction) - [Getting started **Credits and plans** How Briks credits work: holds of 50 and 5, charges for the work done, estimates and builds that wait, what happens at zero, and what each plan includes.](https://briks.dev/docs/credits-and-plans) - [Help **Troubleshooting** What to do when something in Briks is not working: signing in, credits, builds and changes, domains, forms, email, the chatbot, data and teams.](https://briks.dev/docs/troubleshooting) Still stuck? Write to [hello@briks.dev](mailto:hello@briks.dev) with your project's name and what you expected to see. A screenshot helps.