Start with the workflow your team needs, then inspect the application, integrations, and deployment responsibilities that support it.
For business and operations teams
See a concrete example and the scope of a packaged Business Solution.
For technical teams
Inspect interfaces and deployment documentation alongside the application.
Connect an AI client to document operations
The FormKiQ MCP server exposes the OpenAPI specification and selected API operations to compatible clients. It connects to a deployed FormKiQ API using JWT authentication. Review the exposed operations, permissions, and the client/model's processing boundary before connecting sensitive documents.
For AI processing through Amazon Bedrock within the deployment's AWS access model, explore AI Processing and Analysis. The MCP connection and Bedrock module serve different integration needs.
Follow the data and the responsibilities
A customer-managed deployment puts the primary document and metadata resources in your AWS account. Storage location, processing geography, and operational access are separate configuration decisions.
1. Store and organise
Documents, metadata, indexes, and configured logs live in the selected deployment. Define regions, replication, backups, access policies, and key controls for each resource.
2. Process with defined boundaries
Bedrock requests use the deployment's AWS permissions. The selected model and inference profile determine processing geography. A connected signature, credit, or other external service has its own processing boundary.
3. Retain the result and evidence
Keep generated documents, accepted metadata, review decisions, and returned signature evidence with the business file. Assign access, retention, and operational responsibilities.
| Deployment | Account and operations | FormKiQ access |
|---|---|---|
| Customer-managed | Your AWS account and operational policies. | Access only when you grant it for the agreed support purpose. |
| Vendor-managed Enterprise | A dedicated, segregated AWS account operated by FormKiQ. | Defined operational access, policies, and audit records. |
| Hybrid | Customer-managed production, with agreed support in non-production. | Access scoped to the agreed environment and responsibilities. |
For Bedrock, regional and geographic inference options must match your approved boundary; global profiles may route across supported regions worldwide. Review AWS inference routing and FormKiQ security and governance with your deployment requirements.
Evidence you can inspect
Customer experience · migration
RGF Staffing Belgium: 20M+ documents
Micha Van Nijen, Integration Architect at RGF Staffing Belgium, describes the move from Alfresco to FormKiQ and its connection to the organisation's applications.
Read the customer snapshot and original accountEngineering case study · import processing
Tracing and removing an import bottleneck
See the measurements, architecture change, and test conditions behind an optimised 100,000-document import run. The article reports Lambda duration for that workload, with a concurrency caveat.
Inspect the performance case study