FormKiQ modules connect document intake, processing, review, generation, signing, and discovery. Use them within a packaged Business Solution or extend an existing application through FormKiQ's APIs.
Modules are commercial add-ons to Advanced and Enterprise. The selected modules, workflows, and integrations are scoped to your use case; base platform pricing and AWS usage are separate cost components.
Document Generation
Create PDF and Word documents from approved templates and structured data. Prepare agreements, notices, decision letters, and other repeatable outputs, then connect them to the relevant review, signing, and records workflow.
Common fit: financial applications, contract preparation, grants, claims, and correspondence where the same template is populated from controlled information. The implementation defines templates, data mapping, and downstream handling.
eSignature Integration
Connect approved documents to DocuSign through your provider license, then link signing status and the resulting records to the business file. The signing provider processes the document and recipient information under its own account settings and terms.
Common fit: agreements, acknowledgments, and consent workflows where preparation and the records after signing matter. Other providers, including Adobe Acrobat Sign, require a separately scoped integration.
In development: FormKiQ's built-in eSignature feature is targeting an early 2027 release. Current signing workflows use the available provider integration.
AI Processing and Analysis
Classify, extract, summarise, and analyse document content using models through Amazon Bedrock. Connect results to metadata, validation, human review, and the next business step.
In customer-managed deployments, model access uses your AWS account and permissions. The selected model and inference profile determine processing geography; regional or geographic options and global profiles have different boundaries.
Common fit: application intake, contract review, document classification, and other processes where staff need useful information from incoming content. Prompts, fields, mappings, and review rules are configured for the workflow.
Enhanced Full-Text Search
Find documents using their content as well as their metadata. Enhanced search connects FormKiQ to a configured search engine so users and applications can retrieve relevant documents from larger or more complex collections.
Common fit: archives, contracts, case files, and operational repositories where a document's contents matter alongside attributes such as owner, reference, date, or status. Indexing, access filtering, capacity, and search-engine operations are part of the deployment design.
Inspect the search architecture and configuration · Records Management
KnowledgeBase powered by Amazon Bedrock
Support natural-language questions over a selected document collection using retrieval-augmented generation. The solution combines retrieval, model-generated answers, and source references so users can inspect the material behind a response.
Common fit: policy retrieval, research, and case preparation. Collection scope, retrieval permissions, source attribution, answer review, and model geography should be part of the configured workflow.
In customer-managed deployments, Bedrock is accessed through your AWS account. The inference configuration determines processing geography, just as it does for AI Processing and Analysis.
Review model access and processing boundaries · Policy and Procedure Management
Explore the KnowledgeBase retrieval example and access model
Choose modules around the business outcome
| Business need | Typical combination | What to scope |
|---|---|---|
| Application to signed agreement | Document Generation, eSignature Integration, and optional AI processing | Application data, review decisions, approved templates, provider integration, and resulting agreement file |
| Document intake and review | OCR, AI Processing and Analysis, mappings, and review workflows | Document types, required fields, validation, reviewer permissions, and exceptions |
| Repository discovery | Enhanced Full-Text Search and optional KnowledgeBase | Indexing, access filters, retrieval scope, source references, and model processing locations |
All five modules are available as add-ons to Advanced and Enterprise. Confirm the modules, backend version, implementation work, external-provider licenses, and AWS resources required by the selected workflow. Compare editions and pricing.
Questions buyers ask
Do I need to build the application myself?
No. Business Solutions provide packaged applications for supported use cases. Modules supply the selected capabilities, and configuration connects them to your process. APIs also support existing applications and extensions.
What stays in our AWS account?
In a customer-managed deployment, the primary FormKiQ document and metadata resources are in your account. Model requests use Bedrock through that account, with processing geography determined by the model and inference profile. External services such as a signing provider receive the information needed for their stage of the workflow. Review deployment and governance options.
Can we use an existing signing provider?
DocuSign integration uses your provider license and configuration. Adobe Acrobat Sign or another provider should be scoped against its API and your required workflow; an existing license alone does not establish integration compatibility.
How do modules affect implementation and cost?
Modules are selected alongside the base platform, application scope, configuration, and integrations. AWS usage and any external provider charges also matter. We can distinguish those components in a scoped recommendation.
Map modules to your workflow
Bring the document types, systems, review steps, and ownership requirements involved. We can identify the relevant Business Solution and modules, including where a simpler or specialist product fits better.
Book a workflow reviewDocument Gateways · Integration Frameworks · Software comparisons