GitHub - formkiq/formkiq-core: Open-source document management platform leveraging AWS managed services. RESTful API for document storage, processing, full-text search, and metadata management. Multi-tenant serverless architecture with auto-scaling... deployed entirely in your AWS account.

3 min read Original article ↗

FormKiQ Core

FormKiQ is a production-ready document management platform built on AWS serverless infrastructure that deployed in your AWS account. Deploy a complete API-first document layer alongside your application's data tier—handling storage, metadata, search, and access control without the complexity of building it yourself.

Who it’s for

  • Teams building secure file workflows that must remain in their AWS accounts.
  • Regulated workloads needing auditability, retention, and least-privilege access.
  • SaaS platforms delivering per-tenant document storage with isolation and signed links.
  • Ops/support teams needing fast search over PDFs and images without custom pipelines.

Capabilities at a glance

  • Ingest via API Gateway, S3, or email; optional OCR pipeline for images/PDFs.
  • Metadata and tagging for every document plus custom attributes.
  • Full-text/OCR search and filters; show only what each user/tenant should see.
  • Versioning, retention, and audit trails built-in; lifecycle controls via policies.
  • Event hooks via Lambda/SNS/SQS/EventBridge to enrich, classify, notify.
  • SDKs for Java and Python, plus OpenAPI for other languages.

Why teams choose FormKiQ

  • Data and keys stay in your AWS account; IAM-first access control and audit trails.
  • Built-in metadata/tagging, OCR search, versioning, and retention—no custom boilerplate.
  • Serverless stack that auto-scales; no servers to patch or capacity to size.
  • Multi-tenant ready and SOC 2–aligned design for regulated workloads.

Common use cases

  • Records and retention vaults for HR, legal, and finance with audit trails and versioning.
  • Intelligent ingestion: drop into S3/email/API, OCR + metadata tagging, and route via events.
  • Compliance-focused file storage where data must remain in your AWS account with IAM-scoped access.
  • Customer/partner file portals with per-tenant isolation and signed access links.
  • Workflow enrichment: trigger Lambdas on uploads to classify, enrich metadata, notify via SNS/SQS/EventBridge.
  • Searchable knowledge stores over PDFs/images for support and operations teams.

Deployment options

  • Deploy to your AWS account via CloudFormation (Quickstart below).
  • Evaluate in the hosted demo environment (read-only).
  • Inquire about managed workspaces if you prefer a turnkey setup.

Quick Start

  1. AWS deploy: Quickstart Guide (CloudFormation).
  2. Hosted demo: Explore — Email: demo@formkiq.com, Password: tryformkiq.
  3. API walkthrough: Step-by-step to integrate quickly.
    • Requirements: AWS account, CLI/CloudFormation access, Java/Gradle for local builds.

Architecture

Serverless on AWS: Lambda + API Gateway + S3 + DynamoDB + OpenSearch, with optional modules for OCR, Typesense, and event handling.

FormKiQ architecture diagram

Project structure & commands

  • Modules: lambda-* and lambda-*-graalvm functions, AWS adapters (aws-*), shared libs (fkq-*, http*, strings), console UI (console).
  • Templates/assets: src/main/resources/cloudformation, docs/, images/, docker/.
  • Build/test: ./gradlew clean build (full build + tests), ./gradlew test (tests only), ./gradlew spotlessCheck (format), ./gradlew licenseReport (license inventory).

Security, compliance, and scale

  • Data, encryption keys, and access policies remain in your AWS account; IAM secures every interaction.
  • Versioning and audit trails support retention and evidence needs for SOC 2/HIPAA-style controls.
  • Serverless footprint scales with demand; designed for thousands of concurrent requests.

Client SDKs

Client Tutorials

Resources & support

License

MIT License - © 2020-2025 FormKiQ, Inc. See LICENSE for full details.