DOCUMENTATION
Using AI Hero Studio.
What AI Hero Studio actually is, how an engagement runs, and what you do as the customer once we're live.
What Studio is.
A Studio engagement produces one app for one customer. We design, build, and host it. The shape of the app matches your operation — your entities, your terminology, your integrations, your data residency.
AI Hero retains the engineering team. We host. You operate the business that runs on top.
The rest of this page describes how an engagement runs, what to expect, and how the day-to-day works once your deployment is live.
How the engagement runs.
01
Discover.
We sit with your operators. We watch the work — the spreadsheet they patched, the SaaS they bent, the meeting that exists only because the tooling doesn't. We come back with a short architecture proposal and a price.
02
Architect.
We design the shape of the app: the entities, the agent surfaces, the integrations, the data residency. You see the diagram before we write a line of code.
03
Build.
We ship. Code in our repos, infrastructure in a VPC dedicated to you inside our SOC 2 cloud. Reviews happen in your Slack channel. Demoable software lands in weeks, not quarters.
04
Host & keep shipping.
We host the result under SLA. On-call rotation, monitoring, and a backlog that keeps moving — same team, same Slack, no handoff to a separate operations org.
What to expect.
A bespoke app, not a workflow builder.
We build software shaped to your operation — your entities, your terminology, your integrations. Not a low-code canvas you have to assemble.
Agents-in-the-loop, not autonomous.
Every customer-facing surface puts the operator in the seat. Agents draft, retrieve, summarize, and execute under human review. We retain engineering ownership; you retain operating control.
Hosted in a VPC dedicated to you.
Every deployment lives in a per-tenant VPC inside our SOC 2 cloud, provisioned at onboarding. We host under SLA. You operate the business inside it.
Subscription pricing.
Priced as a monthly subscription, not as services-on-the-clock. Architecture changes, fixes, and new features ship inside the engagement.
How you work with us once live.
Your Slack channel.
Day-to-day: a shared Slack channel with the engineers building and hosting your software. Bug reports, feature asks, deployment notices land here.
Status + incident updates.
Live status for your deployment. Incident communication follows the SLA in your contract — on-call is 24/7 for production.
Releases + changelogs.
Every deployment-level change is announced. Major surface changes are demoed before they ship to your production environment.
Reviewable audit log.
Every change to your deployment lands in an audit log you can read at any time.
What your operators see.
Your operators get a surface built around the workflow we ship for you — with bounded agents-in-the-loop wired into the work. Your people stay in control; the agents do the work alongside them.
Identity and access are handled by Auth — a hosted OIDC IdP with passwordless sign-in. Every Studio app we ship trusts the same identity surface.
Beyond the common services, the rest of your app is custom-built. See Solution for the patterns we build today.
Where to look next.
Questions?
Email team@aihero.studio. If you're evaluating Studio for a new engagement, start here.