Your infrastructure. Your data perimeter.
KinetiPlan is designed to run where you decide: in your own AWS account in a US region, or on your own servers. This page shows the reference architecture and states plainly which parts are built, which are planned and which still need verification.
Everything inside the dashed line is yours.
Reference design. Components, region, sizing, backups and support terms are agreed in each customer’s written deployment plan. Items marked planned or to be verified below are not claimed as implemented.
Three models, one product
| Model | Who runs the infrastructure | Status | Fits when |
|---|---|---|---|
| Customer-hosted in your AWS account | You, in a US region you choose; Software Home installs and supports under agreed access rules | Primary model | You want data and keys in your own cloud account |
| On-premises / private data center | You, on your servers and network | Scoped per customer | Policy or clients require your own hardware |
| KinetiPlan-hosted cloud (single-tenant) | Software Home, in a dedicated US AWS environment | Future option | You prefer not to run infrastructure; offered only after controls are evidenced |
What exists, what is planned
| Area | Status | Detail |
|---|---|---|
| On-premises deployment | Scoped per customer | Installation on customer servers is agreed per customer; supported OS and database versions to be documented. |
| Customer-controlled infrastructure | Working in pilot build | The customer owns the account, network, keys, backups and identity provider; this is the design priority. |
| Database architecture | Working in pilot build | One relational database holds plans, census, ledger, projects and audit events, so every workflow reads the same records. |
| Application server architecture | Working in pilot build | Web application plus background jobs and a documented JSON API; runs in private subnets behind a load balancer in the reference design. |
| Backup and recovery | To be verified | Backups run in the customer’s environment; restore procedures and tested RPO/RTO are documented in each deployment plan. |
| Access controls | Planned | Role-based permissions are planned; the pilot build has no role permission model yet. SSO through the customer IdP is planned. |
| Encryption | To be verified | TLS in transit and encryption at rest using the customer’s managed keys are design requirements; evidence per deployment is pending engineering verification. |
| Audit logging | Working in pilot build | Exception resolutions are recorded with notes for the audit trail in the pilot build. A complete, tamper-evident audit log of all changes is planned. |
| Disaster recovery | Planned | Cross-zone or secondary-site recovery is defined per customer; no DR test has been performed yet. |
| API integration | Working in pilot build | A documented JSON API with interactive docs exists in the pilot build; write APIs and webhooks are scoped per customer. |
| Upgrades and maintenance | Planned | Versioned releases, scripted schema migrations, release notes, a test window in a customer staging environment and a rollback plan. |
"Working in pilot build" means the function runs in the KinetiPlan pilot build on synthetic demo data. It does not mean generally available, certified or production-proven. "To be verified" means the engineering team has not yet confirmed it with evidence.
How a release reaches your environment
Release notes and test evidence
Each version lists changes, migrations and the calculation tests it passed.
Staging first
You install it in a staging copy, run your acceptance checks and sign off.
Scheduled production window
Applied by your team or by Software Home under an approved, logged session.
Rollback ready
A database backup and the previous version are kept until you confirm the release.
Evaluating a KinetiPlan-hosted cloud
Some smaller TPAs will not want to run infrastructure. A single-tenant, KinetiPlan-hosted environment in a US AWS region is being evaluated for later. It would be offered only after the controls on the enterprise readiness roadmap are evidenced, including a SOC 2 readiness assessment. Until then, the customer-hosted models above are the offer.
Map your environment with an engineer.
Choose the conversation that fits where you are. Calls run on Google Meet. Nothing on this website asks for participant data.
Frequently asked questions
Can KinetiPlan run entirely inside our network?
Yes, that is the on-premises model. Installation details, supported versions and the support access process are agreed in a written deployment plan.
Does Software Home have access to our production data?
Not by default. The support model has no standing access: a session is requested, approved by you, time-limited and logged.
Is there a hosted version?
Not yet. A single-tenant KinetiPlan-hosted cloud is a future option, offered only after its controls are evidenced.