Hybrid deployment is designed for teams that need rapid onboarding and collaborative implementation support while preserving strict customer control over production infrastructure. Non-production environments can be accessible to FormKiQ teams for setup, configuration, and support, while production remains fully customer-owned and operated.
What "hybrid" means in practice
- Non-production environments: Dev, QA, and staging environments can be FormKiQ-accessible for implementation support, testing, and onboarding collaboration.
- Production environment: Deployed in your own AWS account with customer-owned IAM, encryption keys, networking, and audit controls. FormKiQ has no production access.
- Controlled promotion path: A defined process governs how configurations and deployments move from lower environments into production, maintaining your team's control over what reaches the production boundary.
- Implementation speed: FormKiQ can work directly in non-production environments to accelerate setup, integration testing, and configuration — without requiring your team to manage those environments independently during the implementation phase.
Comparison: Deployment Models
| Customer-Managed | Vendor-Managed | Hybrid | |
|---|---|---|---|
| Data in your AWS account | Yes | Segregated account | Production only |
| FormKiQ team access | None unless granted | Operational access | Non-production only |
| Your team manages infrastructure | Full | No | Production |
When to choose hybrid
- You need faster implementation and onboarding than a fully self-managed model allows.
- Your compliance or security policy prohibits vendor access to production systems or production data.
- You want FormKiQ's implementation support available during setup without compromising production sovereignty.
- Your team has cloud operations capacity for production but wants to minimize involvement in lower environment setup.
Compliance considerations
The hybrid model is specifically designed for organizations where production sovereignty is non-negotiable but implementation speed is a practical requirement. Because FormKiQ access is limited to non-production environments, production data and production infrastructure remain under customer control throughout the deployment lifecycle.
Organizations should define clear environment boundaries and promotion policies before implementation begins to ensure the hybrid model operates as expected under their compliance framework.
Getting started
Hybrid deployment starts with defining environment boundaries and the access model for non-production. FormKiQ can support that planning conversation as part of the onboarding process.
Book a Call