FormKiQ Sites or Separate Instances: How to Choose

Separate departments, use cases and customer workspaces at the right level

Published

Paper-cut illustration of two document folders sharing one deployment, beside folders in separate dedicated deployments.
Department, workflow and customer document spaces can share a deployment; dedicated instances let hosting and operations differ.

HR needs employee files, finance needs invoice records, and an investigation team needs a restricted evidence space. These teams belong to one organisation and can share an AWS region and operating model while needing different document-access boundaries. A regional business unit may also need its own AWS account and deployment.

Use FormKiQ sites for logical document partitions around departments, use cases or customer workspaces. Use separate instances when the AWS account, region or deployment operation must differ. One organisation can combine several sites in a shared deployment with separate instances for business units that need their own infrastructure.

Decide which departments and use cases need their own space

Departmental sites such as hr, finance and legal give each team a separately managed document namespace and access assignments. A use case can also justify its own site: restricted investigations may involve selected people from HR, legal and operations while excluding the wider membership of those departments. The work and its audience determine the boundary.

Within an approved space, use entities and document attributes to organise individual employees, agreements, projects or cases. Classification schemas and configured workflows can distinguish record types and processes within a site. Each new case or document type does not automatically require another site; grouping records still needs the appropriate access controls.

Separate the access decision from the deployment decision

  1. 1. Access

    Who may use the documents?

    Define department or workflow membership, site permissions and the administrators who can act across sites.

  2. 2. Infrastructure

    What can these teams share?

    Check account, region, deployment configuration, upgrades, recovery and service limits.

  3. 3. Verification

    Does the whole route respect that choice?

    Check application routing, document access, search and each configured integration.

Choose from organisational and workflow requirements. A separate stack provides the boundaries configured around it.
RequirementSites in one instanceSeparate instances
Department, use-case or customer document spacesEach site has a document namespace and assigned permissions.Each deployment can contain its own departmental or workflow sites.
Different AWS account or regionSites share the deployment's account and region.Place each stack in the required account and region.
Independent modules, encryption infrastructure or upgrade scheduleDeployment settings remain shared; site-level permissions, metadata and workflows can differ.Configure and operate each deployment independently where required.
Administration, incidents and service limitsCross-site administrators and shared services remain part of the boundary.Account placement, roles and shared dependencies determine the remaining scope of impact.
Cost and operating effortConsolidate the deployment baseline and common operations.Budget for each stack, selected capabilities and the work of maintaining them.

Two stacks in the same AWS account may still share administrators and account-level service quotas. AWS's multi-account guidance explains the additional security, cost-management and quota boundaries available through separate accounts. Check the actual dependency and permission model before treating an instance as independent.

A regional stack also needs a regional data plan. Review backups, logs, indexes, exports and configured processing services alongside the document store. The multi-region architecture guide develops those residency and retrieval choices.

Choose how site permissions will be managed

Automatic Sites derives access from identity-provider groups. Defined Sites provides explicit sites and group-permission assignments and is available in FormKiQ Essentials, Advanced and Enterprise. Both require a deliberate membership and administrator model. A supplied siteId alone does not authorize access; the application and FormKiQ permissions must agree on the permitted department, workflow or customer space.

For example, an administrator with access across sites is suitable for approved administration, while an employee, reviewer or background integration needs access appropriate to its work. Test those paths separately. The security guide describes authentication methods, site permissions and administrator reach.

When moving from Automatic Sites to Defined Sites, follow the deployment guide's user-pool and permission prerequisites. Recreate the required site definitions and group permissions, including access to existing documents, and validate administrator and normal-user routes before the change is accepted.

Worked example: departments and restricted investigations

In this fictional organisation, HR manages employee records, finance manages invoice files, and operations manages routine business documents and incident investigations. These groups can share a Canadian regional deployment and a common upgrade and recovery plan. A European business unit has an internal requirement for a German regional deployment in its own AWS account.

  1. Assign departmental document spaces

    Create Defined Sites for HR, finance and routine operations, and assign the approved groups to each. The HR Business Solution manages employee onboarding and later employment records within the selected HR space.

  2. Give the restricted use case its own boundary

    A warehouse near-miss opens an investigation using the Incident and Investigation Management Business Solution. The organisation places that workflow in an investigations site for approved investigators and reviewers. General operations membership does not grant access to that site. Individual investigation dossiers organise the cases within it.

  3. Place the regional business unit

    Deploy a separate FormKiQ instance in the European unit's required account and region. It can also contain departmental and workflow sites. Record the approved endpoint together with each siteId so applications and background integrations select the intended deployment.

  4. Prove the access boundary

    Check that an HR coordinator can work with the intended employee file and is excluded from finance and restricted investigation records. Test investigator and reviewer access separately, including search and integration results. Verify that regional work uses its approved endpoint.

  5. Prove the operating boundary

    Review a failed integration, an upgrade and a restore against each department's or workflow's agreed scope. Include cross-site administrators and shared processing services in that review. If those shared controls cannot meet the requirement, revisit whether the work needs a separate instance or account.

Multi-tenant deployments for customer workspaces

For multi-tenant SaaS, a provider can use the same model for external customers: sites when customer workspaces can share a deployment, and separate instances when account, region or operating requirements differ. Its application maps each authenticated customer to an authorised endpoint and site. See embedded document management for that product and integration model.

Include licensing and operations in the choice

Core supports sites under its MIT license. Advanced and Enterprise offer multi-instance and multi-region commercial licensing, subject to the agreement. Confirm the permitted environments, regions, selected Business Solutions and modules together. Teams embedding FormKiQ in a product also agree OEM, branding, distribution and support arrangements through the partnership scope. See the edition comparison when planning that scope.

Segregation checklist

  • Identify the departments, use cases, business units and customer workspaces that need separate access.
  • Record which account, region, administrators, services and operating schedules those groups can share.
  • Map each authorised business workspace to the approved endpoint and site.
  • Define site membership, permissions and approved cross-site administration.
  • Verify document, search and integration access with both allowed and excluded users.
  • Check backups, logs, processing outputs and exports against the selected regional boundary.
  • Validate upgrades, failure handling and recovery at the agreed departmental, workflow or regional scope.
  • Agree deployment coverage, selected capabilities and operating responsibilities, plus distribution rights where relevant.

Match the boundary to the work

Sites can separate departments, business use cases and customer workspaces within a shared deployment. Separate instances let infrastructure and operations differ. Choose the document-access boundary and the deployment boundary together, then verify that permissions, routing and operational controls preserve both.

      Start with FormKiQ Core

      The open-source foundation — API-first, deployable into your own AWS account, and free to use. Right for architecture validation and early implementation.

      Get Started Free

      Deploy FormKiQ Essentials or Advanced

      Production-ready editions for departments and complex workflows. Start with a Proof-of-Value deployment or go straight to production.

      Explore Options

      Plan an Enterprise Rollout

      For governance-heavy environments with residency, sovereignty, assurance, and multi-jurisdiction requirements. Talk to us about the right deployment model.

      Book a Call