Who pays the cloud bill on Dedicated?
You do. Praxnote Dedicated runs inside your AWS account — your account, your bill,
your reserved instances. Our Dedicated fee covers deployment, updates, monitoring, support, and the
engineering work to keep your tenant on the same release cadence as Cloud. It does not cover your
underlying cloud infrastructure.
Can we switch from Cloud to Dedicated later?
Yes. We've designed the data model so a Cloud tenant can be migrated to a Dedicated deployment
without rebuilding charts, notes, or audit history. It is a planned engagement, not a button —
but it doesn't require throwing anything away.
What does Praxnote see in a Dedicated deployment?
Operational telemetry only: error rates, latency, version, uptime, AI usage volume (counts, not
content). PHI never crosses the boundary. The cross-boundary telemetry schema is documented on
the security page and is auditable by you on demand.
How do updates work on Dedicated?
Praxnote pushes updates on a scheduled, customer-approved cadence. New features ship to Cloud
first; Dedicated tenants typically follow within a release window we agree to in the contract.
Security patches are out-of-band and applied as soon as you approve.
Why is there a paid pilot instead of a free trial for Dedicated?
Because deploying Praxnote into your cloud is real engineering work — provisioning, IAM setup,
integration testing, training. A free trial doesn't reflect that effort honestly, and a free
pilot would set the wrong expectations for either side. A paid pilot is short, scoped, and lets
both of us decide whether the long-term contract makes sense.
Can we self-host Praxnote without Praxnote operating it?
No. Praxnote is a proprietary product and we operate every deployment ourselves. Dedicated is
"your cloud, our hands" — not "your cloud, your hands." If you need fully self-operated
software, Praxnote is the wrong choice.