Build an agent the way you grant a key.
Agent Studio is where a Forge agent is built. An author composes the agent's tools and data boundary from a pick-list the platform has already filtered to what they may wire, validates the definition against the published grammar, test-drives it in a sandbox that cannot write, and publishes an immutable version that re-enters human review.
Tools and data classes come from a pick-list the platform computes — the registry entry's declared maxima intersected with what the author's own token may invoke. An author cannot wire a capability they do not hold; authoring is a projection of authority, never a second path to it.
Definitions validate live against the same versioned JSON Schema the runtime interprets and serves. The first-party Studio and third-party builders share one contract — no hand-synced copies to drift apart.
A draft runs against the real platform with every action forced into compute-and-roll-back preview, under the author's own credentials. The effects are visible; nothing durable is written. A good run is one click from becoming an eval case.
Publishing mints a new version of the registry entry that re-enters review before it is installable. Per-tool confirmation is set at authoring time — and actions the registry marks confirm-required cannot be relaxed by the author.
The hospitality ontology, action engine, connectors, conformed metrics, and public contracts — HTTP, MCP, and generated SDKs — plus Explorer, the operator console.
The dedicated cloud: your own single-tenant Forge cell — its own Postgres, region, and jurisdiction — with governed agents and open-weights models served inside the boundary.
AI products on the same public contracts as every partner — Forge Agents, the first-party runtime, and Talos, its flagship operations agent.
The flagship operations agent: a versioned definition, evals that gate release, and trust measured as conformed metrics.
The PMS: purpose-built screens for arrivals, folios, night audit, housekeeping, and groups & events — running on the governed ontology.
The golden record: entity resolution that recognises the same guest, company, or property across every source system in the portfolio.
Embedded payments across every Aerandil product: the card rail, card on file, deposits and payment requests, no-show fees, refunds and disputes, each property's own merchant account, Charge to key — and Watchtower, the fraud network every hotel on the rail feeds.
Forward deployed
Aerandil is in private development. The next milestone is working with design partners who operate complex, multi-system hospitality businesses.
Design partner channel coming soon.