Most document platforms make you accept their infrastructure. FormKiQ inverts that model. Whether you need full ownership of your AWS environment, a vendor-managed deployment in a segregated cloud account, or a hybrid model that keeps production in your hands while giving FormKiQ teams access to lower environments — you decide how much control to take and where.
Jump directly to the deployment and jurisdiction topics most relevant to your program:
FormKiQ supports three primary deployment models. Each can be scoped to supported AWS regions, giving you precise control over data location and infrastructure access.
Deploy entirely into your own AWS account. Your data, keys, IAM, and access boundaries remain under your control.
FormKiQ operates a dedicated, segregated AWS account managed by FormKiQ teams for faster turnkey onboarding.
Non-production can be shared for support/onboarding while production remains customer-controlled with strict access boundaries.
Data residency and privacy obligations are jurisdiction-specific. FormKiQ deploys into supported AWS regions, and its architecture — role-based access, auditable metadata, configurable retention, and lifecycle controls — can be aligned to each geography's requirements.
Across deployment models, FormKiQ provides governance-sensitive controls: customer-controlled encryption, segregated access boundaries, auditable workflows, and defensible lifecycle management.
Important guardrail: FormKiQ does not claim blanket legal compliance with any law or jurisdiction. It provides architectural building blocks your legal and compliance teams validate and configure for your obligations.
The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.
Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.
For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.