AI website system · frequently asked questions
Your questions about the AI website system, answered.
A note on these answers: Several answers below simply confirm that nothing changes with the AI website system approach versus a traditional website build. Where that is the case, we say so.
01 How are updates managed?
You make day-to-day edits just by chatting with an AI assistant. You describe the change you want in plain language. You never touch any code or technical tools.
Every change is drafted first, so you can preview it before it goes live. When you approve it, it publishes to your website. A full history is kept, so you can roll back to any previous version at any time.
02 Who can make changes, and can we control who is allowed to publish?
Yes. Access is managed with team roles, so you decide who can make changes and who can publish them live:
| Role | Draft changes | Publish live | Manage members | Billing & team |
|---|---|---|---|---|
| Owner | ✓ | ✓ | ✓ | ✓ |
| Admin | ✓ | ✓ | ✓ | — |
| Editor | ✓ | ✓ | — | — |
| Contributor | ✓ | — | — | — |
The Contributor role is especially useful for review and approval: staff can prepare and draft updates, while a smaller group of Editors, Admins, or Owners reviews those changes and publishes them live.
03 What happens if Claude changes its model?
AI models keep improving, so a newer model is typically more capable than the one before it.
A model change also cannot affect your live website. Your site is already built and published as finished pages. The AI only edits a draft when you ask it to, and you preview and approve every change before it goes live.
You are also not tied to any single AI company. Many AI assistants can make these edits, so if one is not performing well, we can use another.
04 What is the disaster recovery plan?
Our architecture is the disaster recovery plan. Traditional disaster recovery exists to answer what happens when the server dies, data is lost, or a change breaks something. Our setup answers all three by design, not after the fact.
Every version of your site is stored and reversible, so any bad change is undone by instantly republishing the last good version, usually within minutes, with no data loss. The site has no database to corrupt.
It is served from a globally redundant network with no single server to fail, and the complete source of your site is preserved independently, so even if the hosting provider has a disruption, the site can be moved and republished elsewhere.
| Disaster scenario | What happens | Recovery time |
|---|---|---|
| Bad change / site breaks | Every version is reversible; republish the last good version. | Seconds to minutes |
| Site content lost or corrupted | A full history of the site is preserved; republish from any point. | Minutes |
| “Data loss” | There is no database, so there is nothing to corrupt or lose. | Effectively zero risk |
| Hosting provider issue | Static pages stay served from the global network; worst case, the same source republishes to another host. | Hours, and rare |
| Account compromise | Revoke access, restore from the preserved source, republish clean. | Minutes once detected |
| DNS / domain issue | Recover through the domain registrar and repoint DNS. | Hours |
In the rare event of a platform-wide provider outage, your site’s source is fully portable and can be republished on alternative infrastructure. For any urgent issue, see “Who supports it when something breaks?” below.
05 What kind of uptime can we expect?
Your site is served from a globally redundant edge network with no single server to fail, so it is built for very high availability. There is no single machine that can go down and take the site with it.
06 How does performance compare to a traditional WordPress site?
The AI website build is faster. Your pages are pre-built into finished HTML and served from the location closest to each visitor, so there is no server software assembling the page on every visit and no database to wait on. Pages load quickly and stay fast even under heavy traffic.
Faster pages also tend to help with search rankings and conversions, since both search engines and visitors reward sites that load quickly.
07 How is ADA compliance reviewed and tested? Unchanged
This does not change with the AI website system approach. We complete the ADA statement of work in our agreement: before launch, we scan the site and resolve the issues the scan identifies. After launch, we rescan on a quarterly basis and report the results to you.
08 How are rates updated? Same, but easier
This works the same as a traditional build, and AI makes it easier. Your rates live in one central location on the site, so there is a single source of truth. Updating them in that one place updates them everywhere they appear.
You tell the AI which rates to change, or upload your latest rate sheet, and it updates them for you. You confirm the changes before they publish. You can also schedule rate changes to publish automatically at a future time.
09 How is security audited? Unchanged
This does not change with the AI website system approach. Before launch, and on a quarterly basis after launch, we run security scans so we can catch and address vulnerabilities.
The AI website system architecture also reduces what can be attacked in the first place. The site is built as static pages with no database, no plugins, and no login-based admin dashboard, which removes the most common targets in a traditional website breach.
10 Where does our member data live, and is it secure?
Your website itself stores no member data and has no database. Sensitive actions like online banking, account opening, and loan applications happen inside the vendors’ own secure systems, not on the website. There is no pool of member data on the site for an attacker to reach.
11 How does it integrate with online banking, account opening, loan applications, and third-party tools? Unchanged
This does not change with the AI website system approach. Online loan and account applications are simple links to the third-party tools. Embedded integrations, such as online banking, use the code the vendor provides.
12 What happens if we stop working with MetriFi?
You are not locked in. The complete source of your website is preserved and fully portable, so it can be moved to other hosting if you ever choose to.
13 Who supports it when something breaks on a Saturday night?
Our team is on call 24/7/365 for emergencies. If something breaks, you submit an emergency support ticket. Our team is notified instantly and begins investigating and working on the problem right away. Response times are covered by the SLA in our agreement.