Project settings
Each project's page on the dashboard is organized top to bottom by how often you'll need things: the AI Builder's quality first, then hosting, then the plugin cards, with experimental knobs and destructive actions at the very end.
AI Builder quality
Which AI brain builds your site — three cards, always visible:
- Medium — fast and affordable, great for most sites. The default.
- High — stronger reasoning for complex apps.
- Pro — the most capable model, for demanding builds.
Below the cards sits the Vision support checkbox (recommended, on by default): with it, the AI can see — it looks at your pages and the screenshots you send, and visually double-checks its own work while building. Each card shows the live price of the exact model your combination selects, so toggling Vision updates the numbers in place. Changing anything reveals a Save button; saving applies right away and restarts the project.
Domain
Two things live here:
- Your startupjs.ai address — the
something.startupjs.ainame. Rename it anytime; the old address stops working, so re-share links after a rename. - Your own domain — connect
www.yourbakery.com(or any domain you own). The section shows exactly one DNS record to add — an A record pointing your domain at the platform's address, added wherever you manage the domain's DNS (usually your registrar). Once the record is live, the first visit to your domain sets up its security certificate automatically — typically within a minute. Both addresses keep working; mobile app links switch to your domain automatically.
Compute
Your plan includes a pool of compute units, and this dial assigns how many this project gets. More units = more memory and more storage (1 GB per unit) for the site, and a higher daily email cap. The section shows current storage use against the limit. Most sites are fine on one unit — raise it if the site handles lots of data or traffic.
Generate images
Image generation lives with the plugin cards now: the Generate images card opens a page where you pick Off / Medium / High (with the approximate cost per image). Details: Images.
Assistant engine (Experimental)
At the bottom of the page, before the Danger zone. Standard is the classic AI Builder — fast and proven, right for most sites. Advanced is an experimental deep-work engine: it works on your site like a programmer on a codebase and remembers the full history of your project between chats — it can handle bigger builds, but is usually slower and a bit pricier.
Share admin access (Experimental)
Give another person the same admin access to this project as you have — they can open the site, chat with its AI Builder, and change every setting. Add them by the email they use on startupjs.ai (they need an account first — if the email isn't found, ask them to sign up and then add them). They'll get an email with the link, and the project appears in their sidebar under Shared with me.
Two things always stay yours alone: deleting the project and changing who it's shared with. One thing to know before you share: their AI Builder usage on this project counts toward your plan, just like your own.
To take access back, open the section and remove them — the project disappears from their dashboard immediately.
CMS version (Experimental)
In the Experimental group at the bottom of the page — you will rarely need it: updates are automatic, and when one needs your attention the card itself tells you what to press. The CMS is the engine your site runs on: its pages, data, plugins and the AI Builder. Every site runs on a CMS version, named by the month it shipped (for example "September 2026"). The section shows which one your site runs (and whether an update is being checked, waiting for you, or held) and offers one choice:
- Automatic (recommended) — your site moves to new CMS versions as they ship; on paid plans only after its own checks pass on a copy of it. Fixes for your current version are always applied; they don't change how your site works.
- Ask me first (paid plans) — the checks run on a copy, then your site waits for your go-ahead: you get an email and an Update now button.
- Hold on the version you run today — nothing moves until you switch back. Fixes for that version still reach it; bigger changes wait. Versions stop getting fixes 180 days after release. There is no way to move a site to an OLDER version — only Undo (7 days after a move) goes back, and only to the version it came from. Switching a held site back to Automatic runs the checks on a copy first (paid plans), then moves it.
Before your site moves to a new version, we run its own checks on a copy of it. If they don't pass, your site doesn't move. If your site has a test suite (ask the AI to write one), that suite runs; otherwise every page is opened headlessly and compared with how it renders today. You see the result under CMS version afterwards: a green receipt with Undo for 7 days, or a red one that says what did not pass — your site keeps running exactly as before, and you can Fix it with the AI on a copy (the AI works on a copy of your site on the new version, starting from what did not pass; uses a little of your credit; you preview, then update) or Update anyway. On paid plans you can also pick Ask me first: your site waits for your go-ahead once the checks pass.
Bigger updates
Now and then a CMS version changes how sites are built (a "bigger update"). Your site never moves to one by itself: it stays on its current version, which keeps receiving fixes, until you decide. The CMS version section explains what changes in plain words and offers Prepare the update with the AI: the AI migrates a copy of your site on the new version and runs your site's checks on it. This uses a little of your AI credit (about $1–2). When the copy passes, you get an email and two buttons: Preview the migrated site (a private link, valid for 15 minutes) and Update now. If the copy does not pass, nothing changes; you can try again or export your site. After moving, Undo is available for 7 days when the update did not change how your data is stored.
Environment variables
An advanced section you'll normally never open: named configuration values passed privately to your site. Some plugin and connection setups store their credentials here — always write-only. If a guide tells you to add a variable, this is where.
The Danger zone
- Restart — turns the site off and on (a few seconds of downtime, data untouched). The classic first move if something seems stuck.
- Lock — parks the project: it stops running and frees its compute units for other projects, but keeps all data and its domain. Unlock anytime.
- Delete — moves the project to the Trash (restorable for 7 days). You'll type the project's name to confirm.
BYO projects
Projects that host your own app have two extra sections — GitHub repository (which repo and branch to deploy) and Deploy log — covered on that page.