Skip to main content
Resources · Documentation

The documentation for your build.

Detailed documentation and a working sandbox ship with the engagement, written against your actual deployment in your own cloud. This page is the map: it outlines what gets documented, and how to get access.

What gets documented

Six areas, written for your deployment.

GETTING STARTED

The Diagnostic

What the 5-day Diagnostic covers, what we need from you, and the readout you receive at the end. The honest entry point, before any code.

Prospective & client
ARCHITECTURE

In-cloud deployment

How agents are deployed inside your own GCP, AWS, or Azure account, with diagrams of the services, data flow, and boundaries for your environment.

Client access
SECURITY

Access model

Least-privilege IAM roles you grant and revoke, the audit trail, the kill-switch, and where the BAA fits for healthcare engagements.

Client access
OPERATIONS

Runbooks & monitoring

The runbooks we operate against: what we watch, how we tune, how alerts route, and what you see day to day while the system runs in your cloud.

Client access
INTEGRATIONS

PMS & warehouses

How agents connect to your practice management system and your warehouse, documented per connector against the systems you already own.

Client access
HANDOFF

Ownership

What you own, where it lives, and how ownership transfers. We operate the system, and the documentation makes the line of ownership explicit.

Client access
How to get access

Docs follow the engagement.

Clients receive the full documentation set and a working sandbox, scoped to their own deployment, during the engagement. There are no public API keys or sample endpoints to copy: everything is written against your cloud, your data, and your access model. If you are evaluating us, start with the 5-day Diagnostic. It is the honest first step, fixed fee at $3,500, refunded against the build if you move forward.