Add document capabilities to the product your customers already use. FormKiQ's API-first platform provides storage, metadata, search, and document operations on AWS, while your SaaS application owns the customer experience.
Independent software vendors can use sites for logical tenant separation within one deployment, or separate instances when customers need their own infrastructure or regional boundary. White-label and OEM arrangements are available through the partnership model, with commercial terms scoped to the offering.
Explore a lending-product exampleA document layer behind your application
- 1 · Product experience
Keep users in your workflow
Your application presents the upload, case file, search, and review experience. Connect it through FormKiQ's APIs and SDKs.
- 2 · Document services
Use governed document operations
Store documents, attach business metadata, apply site permissions, and connect events to processing. Select commercial workflow and access capabilities for the product's requirements.
- 3 · Deployment
Choose the customer boundary
Deploy into the agreed AWS account and region. Define who operates updates, identity, monitoring, recovery, and customer onboarding.
Multi-tenant sites or separate instances?
| Requirement | Sites in one deployment | Separate instances |
|---|---|---|
| Customer document spaces | Each tenant can have a site with its own document namespace and assigned permissions. | Each customer can have a separate FormKiQ stack. |
| AWS account and region | Shared by the deployment; a site is a logical access boundary. | Can be separated by account and region to meet customer requirements. |
| Platform operation | Shared infrastructure, service quotas, and deployment updates. | Separate configuration, rollout, monitoring, and recovery responsibilities. |
| Edition and licensing | Core supports sites; Essentials and above add Defined Sites and explicit permission assignment. | Advanced and Enterprise offer multi-instance and multi-region commercial licensing, subject to the agreement. Core retains its MIT license. |
Sites do not provide separate AWS accounts, encryption infrastructure, or regions. Choose instances when those boundaries matter. See the deployment and tenant guide for the operational tradeoffs.
Illustrative architecture · fictional SaaS product
Documents inside a lending application
A software vendor serves credit unions through a branded application. Borrowers upload supporting records, staff review the file, and an approved application proceeds to agreement preparation.
The product maps each customer workspace to an authorized FormKiQ site and attaches an application reference and document type to each record. Its backend derives the permitted tenant from the authenticated session and validates access on every request. A caller-supplied site ID alone is not authorization.
The Financial Application Management Business Solution delivers application intake, review, and agreement workflows. A vendor can scope that application with its product integration, or use FormKiQ APIs within an existing lending interface. Customer-specific fields, decision rules, and system mappings are configured around the process.
A customer requiring a separate AWS account or region uses a separate instance. Selected modules can add Document Generation or AI Processing and Analysis. Those modules and integration scope are agreed separately.
Evaluate the product and commercial model together
- Define tenant provisioning, access, support access, and offboarding; test cross-tenant requests.
- Map document IDs and metadata to your application's customer and business records.
- Select the edition, modules, and packaged solution required by the workflow.
- Agree branding, distribution, OEM rights, permitted deployments, and support responsibilities.
- Plan updates, backups, recovery, export, deletion, and any residency commitments.
- Measure representative uploads, processing, and search before estimating AWS and module usage.
Inspect authentication and access controls · Explore SDKs and API evidence · Compare editions
Embed the capabilities your product needs
FormKiQ fits software teams that want document APIs, configurable workflows, and AWS deployment control within a branded product. Choose a tenant model and a representative customer journey, then scope the platform and partnership around that delivery model.
Plan your embedded document offering
Bring the customer workflow, tenant model, and hosting requirements. We can review the integration, licensing, and operational boundaries together.
Book a product architecture review