The honest answers.
Including the ones that are easier to leave out.
Running the loop.
Do I approve changes before they go live?
No. Vivere ships, then emails you what changed and why. One git revert undoes it. There is no pre-deploy approval gate, and that is a deliberate design decision rather than a missing feature.
Why is there no approval step?
An approval queue reintroduces the exact bottleneck Vivere exists to remove. The moment a change waits on a person, the loop runs at that person's speed. Review happens through the email you get and the revert you always have.
How often does it run?
Every 1,000 views on the page, or every 10 days, whichever comes first. Volume is the better trigger, and the clock stops the loop stalling on a quieter page.
Can it run on more than one page?
The loop is per page. Each page has its own trigger, its own history, and its own run.
What happens if there is nothing worth changing?
The run stops. The Analyst is the only stage that can halt the pipeline, and not having enough evidence to act confidently is exactly what that authority is for.
What could go wrong.
What if it makes the page worse?
It waits for statistical confidence before acting, so it does not chase noise. If a change still turns out to be wrong, you revert it like any other commit.
Will it slow my site down?
No. Changes are real code in your repo, not injected scripts. No flicker, no speed hit, no search ranking damage.
Will it go off brand?
A design system agent reviews every planned change against your existing components before anything is built.
Can I stop it touching certain things?
Yes. Restrictive zones let you mark any component or file completely off-limits to every agent. Pricing tables and checkout flows are the usual candidates.
Who checks the legal side?
A legal sub-agent runs a live search for current compliance rules when a change touches something that warrants it. Legal pages do not need marking as restrictive because this already covers them.
Where does the code actually run?
In isolated compute. Agents read, write and test inside a sandbox, and nothing reaches production until every gate has passed.
How do I undo a change?
One git revert. Because changes are ordinary commits, rollback is an ordinary rollback. There is nothing proprietary in the way.
Whether it suits you.
How much traffic do I need?
Around 10,000 monthly visitors per page. Below that there is not enough signal to trust a result, and the Analyst will keep halting runs rather than acting on noise.
What does it work with?
Git-based codebases with component-level architecture. React and Next.js today.
Will it work on my site builder page?
No. Vivere needs a repo it can patch at the component level. A page with no accessible codebase is not something the Builder can work on.
What analytics does it need?
Behavioural analytics on the page. Vivere reads from PostHog today.
Money and timing.
What does it cost?
Not decided yet. Vivere is pre-launch, and quoting a number now would be making one up. Waitlist members hear first.
When can I use it?
Vivere is not open to customers yet. The waitlist is how you find out when that changes.
Do you have customers today?
No. Vivere is being built, and any product data you see on this site is sample data and labelled as such.
Still have a question?
Join the waitlist and ask it. We answer waitlist mail ourselves.