Your hosted web app

Your app runs in its own AWS environments, kept apart from every other customer's. There are two copies of it:

• Staging — where your agent tries changes. The approval cards call it your test site. Nobody but you and your team uses it.
• Production — the copy your customers use. It only changes after you approve.

The agent builds and ships changes to staging by itself. Production changes always wait for you.

On the new-agent form, tick AWS included (we host your app) and choose a template. Setup takes roughly half an hour. While it runs, the setup page shows a ring that fills as each step completes, and the agent's page gains a Hosted App tab listing the same steps.

Once setup finishes, the Hosted App tab shows the staging and production addresses and, under Sign-in for your app, who can sign in to each copy. Add yourself first, then your team.

Ask in a chat with your agent, the way you would ask a developer. Say what you want and why; you do not need to say how. Good first asks:

• “Add a Referred by field to the contact form and show it in the contact list.”
• “Rename the Proposal stage to Quote sent everywhere.”
• “Import these contacts” with a spreadsheet attached. The agent maps the columns to your fields and shows you a review before anything is imported.
• “Send me a summary of new deals every Monday morning.” It appears under Automations, where you can see each run.

The agent explains its plan in plain words before it starts, ships the change to staging, and then asks you to check it.

Changes to your records work the same way. Try having your agent add or modify a lead in your staging app. The same can be done on your live app with a simple message once your agent has a sign-in there, and specific changes can even be triggered by things like emails or meeting transcripts: your agent can move deals along and keep the business tracked for you, and build deeper automations from there.

Every change goes through two cards in your Inbox, under Approvals:

1. Check it on staging. The card says what changed in plain words, links to your test site, and suggests what to try. Press Looks right, or Needs changes with a note saying what to fix. The agent reads the note and tries again.
2. Approve it for production. After Looks right, production waits for a separate decision. The card names the exact version you checked, who checked it and when. Press Approve production and the change goes live.

The history under the open cards keeps the last two weeks of decisions, so you can always see who approved what and when.

• Change production without your approval. Staging is the agent's; production is yours.
• Touch production secrets. Passwords, keys and connections for the live app are out of its reach.
• Delete your data to make a change. Staging has its own copy of the data, so nothing the agent tries there reaches production records.

You pick one when you create the agent. Each is a complete, working app on day one.

• CRM — contacts, companies, deals, activities and notes. Sign in with your own passwords and invite your team.
• Client portal — your clients sign in and see their own projects, documents, invoices and messages; your staff manage everything.

Hosting uses two of your credits: one for the agent and one for the app. A plain agent uses one. See How your agent works for how credits are counted and released.

The production database keeps automatic backups for 14 days and is protected against deletion. A change that would remove data needs your approval like any other production change. If you delete the agent, both databases and the app's files are backed up first and kept for 90 days.

If something looks wrong with your app, or a setup step has stopped, use Report an issue on the Support page, or email hello@isomorphlabs.io. Include the agent's name.