How do I embed document management into my SaaS product?
Use FormKiQ as an API-based document layer behind your own interface. Your application connects business records to document IDs and uses authorized APIs for upload, metadata, search, and processing. Sites provide logical tenant separation within a deployment. Choose separate AWS deployments when customers need independent infrastructure, regions, operations, or account boundaries.
Design the application boundary
Start with one business flow: a customer submits a document, staff review it, and the customer sees its status. Decide which system owns the customer identity, business record, document metadata, and approval decision. Your UI can remain part of the SaaS application while FormKiQ handles document operations.
Map the authenticated customer to a permitted site on the server or through verified site grants. Treat a caller-supplied siteId as a request to authorize, not evidence of tenant membership. Keep administrative and background-processing identities separate from end-user access.
Prove tenant isolation
Test a customer listing, searching, downloading, and requesting another customer's known document ID. Include artifacts, processing results, exports, and integration callbacks. Test with ordinary users rather than an administrator that can read every site.
Plan provisioning, account closure, retention, backups, upgrades, and usage attribution alongside the API integration. Logical separation shares deployment resources and service limits; separate instances are appropriate where that shared boundary is insufficient.
Edition and configuration
Core supports sites and document APIs. Commercial licensing for multi-instance operation, selected modules, and OEM or reseller use must match the engagement.