Build on top of AI
Bota is a launch studio. Give it a description or a résumé and it composes the site, sets the type and colour, writes the sections, and sends the project through the compiler verifier when it is available.
Free to start · plans and credit costs are listed in the app, where they are enforced
The brief
01Outcomes
Each recipe carries its own anatomy, motion and typography rules, so a portfolio isn't a business page with the words changed. These three were composed for this page — they aren't customer sites.
Agency recipe · Editorial style. Wide margins, one serif at display size, an index instead of a card grid. The photograph is the only thing allowed to be loud.
Portfolio recipe · Bold style. The work leads and the words follow it. Captions are set in mono, at a size that assumes you came to look.
Product launch recipe · Premium style. Tighter grid, one accent, a panel that shows the thing working instead of a paragraph claiming it does.
02Sources
Point Bota at something that already describes the work. It reads it into facts, shows you what it found, and asks only for what is missing. Instagram and LinkedIn use this same review flow when the workspace's social importer is connected.
We're a two-chair dental clinic in Chilonzor. Check-ups, whitening, braces for kids and adults. Open Saturdays, and we speak Uzbek, Russian and English.
Read as facts
Nothing here was inferred. What you didn't say — prices, a team page — is left out of the composition rather than filled in.
Small-run stoneware. Open studio first Sunday. DMs for commissions.
Read as facts
Bota keeps public profile and post references for review; it does not copy social photographs into the project. Add the images you choose in the workspace.
Read as facts
A profile is a career, not a personality. Bota keeps the roles and the dates and asks you for the one or two projects worth showing.
Read as facts
A résumé is the densest source there is — and the one most people already have. It becomes a personal site, not a PDF with a background.
Every answer goes in as a fact, never as prose for a model to interpret. Blank stays blank: Bota composes around what it doesn't know instead of inventing it.
03Direction
Six recipes, five styles, and a brand kit that the composition actually obeys. Change either below — the sample is live, not a screenshot.
Style
Brand colour
Pick anything. The lightness of your colour is solved numerically until it clears AA as text — in both themes — so a brand can't be chosen into an unreadable page.
A recipe settles the sections, the motion and the typographic rules before a word is written. It is also why the same brief twice does not come back as two different products.
When an imagery provider is connected, Bota can source stock or create imagery from your brief and brand. Where media generation is enabled, Motion Lab saves stills and video into a library your projects share; durable video jobs continue even if you close the tab.
Every motion primitive degrades to visible — reduced motion never leaves content stranded.
04Craft
When the verifier is available, the real TypeScript compiler checks each candidate. If it fails, the diagnostics go back with the file and line, the project is repaired, and it is checked again.
If the checker itself is down, the generation still lands — a verifier outage is not a reason you can't work.
Every band is its own file, so an edit can be scoped to it: rewrite the hero, or only the copy, or only the motion. A scoped edit that touches anything outside the section you named is rejected and retried.
Pick a section, then remix it — the rest of the page is untouched, which is the whole claim.
Scope src/sections/Hero.tsx src/sections/Work.tsx src/sections/Contact.tsx
Generations, chat edits, remixes and brand changes all commit the same way. Restoring is immediate, and a failed generation doesn't land at all — there is no half-written project to clean up.
05Yours
A zip of what you previewed: Vite, React, Tailwind, one file per section, the config, and the images inlined as assets. npm install and it runs — nothing in it points back at us.
Where publishing is enabled, Bota runs your project's real build and swaps the live version atomically, so a visitor sees the old build or the new one and never a half-copied directory. Rolling back doesn't rebuild. Published sites use an origin separate from your account.
On BYOK-enabled workspaces, connect an OpenAI, Gemini or Claude key and generations run against it. Those runs cost fewer platform credits because Bota isn't paying for the model. Remove the key whenever you like.
Plans, credit balances and what each action costs are resolved from one catalog inside the app — so that is where they are published, rather than on a marketing page that can drift out of date.
FAQ
A real front-end project — Vite, React and Tailwind, one file per section, with the config and assets a project needs. The preview you scroll is that project running in your browser, and it is the same project you export.
No. Describe the work or upload a résumé. The studio also has Instagram and LinkedIn import panels; social extraction activates when that workspace's importer is connected. Whatever the source, you review the facts before generation, and what you didn't provide is left out rather than invented.
When BYOK is enabled for the workspace: OpenAI, Gemini or Claude, connected in settings. Generations then run against your key and cost fewer platform credits. Remove it at any time.
Ask for a correction in chat, remix the one section that's off, or edit the file by hand. If it went properly wrong, restore an earlier version — every change is one, and restoring is immediate.
Yes. Download the zip whenever you like, run it locally, commit it, host it wherever you want. Nothing in the output depends on Bota to keep working.
When a photography provider is connected, Bota selects stock or generated imagery according to the plan. Anything you upload is used as-is. Stored project images are inlined into the build, so a published site never depends on a temporary hotlink.
Your turn
Free to start · no card · export the project whenever you want it