ArkCase Enterprise (self-managed)
Configurable case management platform with FOIA and investigative solutions.
5 sources checked by an editor on · Product website ↗
Read this page as JSON or Markdown.
Deployment terms: BYOC · control plane · data plane · private offer
· Open requirements shortlist · Estimate operating costs
Compare this listing with another →
What lands where
Supplied by
Vendor or project
Arrange the enterprise on-premises deployment to physical or virtual machines in your data center.
Runs in
Documented customer environment
Persistent case-management application and integrated document/workflow services.
- AWS: Customer cloud account
- AWS
Servers / containers
Operated by
Your team
Agree the installation, support, security, storage and upgrade responsibilities for the self-managed deployment.
Deployment boundaries by provider
- AWS: Customer cloud account · Customer-operated
Resources in the customer's cloud account, subscription, project or tenancy. Managed cloud services still have shared responsibilities.
ArkCase vendor-maintained Helm deployment tested on EKS ↗ · Source checked 2026-11-12
Application operations and account ownership are separate from infrastructure operations. Confirm external services, telemetry, support access and backup destinations for the chosen path.
| Install method | Arrange the enterprise on-premises deployment to physical or virtual machines in your data center. |
|---|---|
| Infrastructure | Servers / containers The Enterprise product explicitly supports physical or virtual machines in the customer data center; classified as servers. |
| Licensing model | Not specified The vendor distinguishes free Open Source and licensed Enterprise Gold/Platinum tiers. The reviewed sources do not establish the complete license grant for every module in the listed Enterprise FOIA/investigations configuration; do not assume all enterprise code is OSI-licensed. |
| License | Enterprise licensing and module terms require a vendor quote; a separate open-source core edition exists. |
Buyer diligence
Answers apply to the reviewed edition and deployment. Expand a row for qualifications and sources.
How to read these facts
Not researched means no field-specific review is recorded. Not confirmed means sources were checked but did not establish an answer. Availability, eligibility and edition-dependent findings retain the scope given in their evidence. A vendor’s hosted-service certification does not automatically cover your deployment. Evidence coverage is not a feature score.
4 of 12 fields researched (33%) · 2 documented · 2 unresolved. Evidence coverage is not a feature score.
- Single sign-on
DocumentedEvidence and scope for Single sign-on
The Enterprise feature page states SSO and PIV/CAC authentication capabilities. It does not specify protocol or current identity-provider entitlement in that statement; confirm the selected implementation.
ArkCase Enterprise feature statement; not a protocol-compatibility certification · Source ↗ · Reviewed 2026-11-14
Documented · Editor reviewed.
- Deployment artifact / IaC
Not confirmedEvidence and scope for Deployment artifact / IaC
The current public Enterprise and support material does not establish a release-matched self-managed installation artifact. Historical dependency-specific instructions and the open-source distribution do not establish the complete current Enterprise delivery stack; obtain vendor package and installation instructions.
Current ArkCase Enterprise customer-managed delivery artifact remains unconfirmed · Source ↗ · Reviewed 2026-11-21
Sources checked — unresolved · Editor reviewed.
- Minimum footprint / sizing
Not confirmedEvidence and scope for Minimum footprint / sizing
The EULA assigns hardware and supported-stack obligations to the customer but does not publish quantitative Enterprise production sizing. Obtain application, content repository, database, search, transformation and HA resource requirements for the selected release/workload.
ArkCase Enterprise production capacity remains unconfirmed · Source ↗ · Reviewed 2026-11-21
Sources checked — unresolved · Editor reviewed.
- License pricing
DocumentedEvidence and scope for License pricing
The vendor EULA defines commercial software/support rights and requires operation on an ArkCase-supported stack, timely updates and customer-provided equipment. Pricing distinguishes named-user and enterprise offerings. Obtain the selected self-managed order and support terms rather than applying a cloud price to every installation.
ArkCase commercial Enterprise software/support framework; order-specific entitlements · Source ↗ · Public plan distinctions ↗ · Reviewed 2026-11-21
Documented · Editor reviewed.
Show all fields (8 not researched)
- Marketplace delivery
- Not researched Supply a public source.
- Cloud commitment eligibility
- Not researched Supply a public source.
- SCIM provisioning
- Not researched Supply a public source.
- Compliance attestations
- Not researched Supply a public source.
- Security controls
- Not researched Supply a public source.
- Air-gapped operation
- Not researched Supply a public source.
- Operating cost estimate
- Not researched Supply a public source.
- Release snapshot / cadence
- Not researched Supply a public source.
Scope & considerations
The Enterprise product page documents on-premises operation and the FOIA guide lists self-managed options. The pricing page emphasizes cloud plans; confirm the contracted deployment and modules.
Category fit
- Freedom of information & public access
- FOIA/public-records solution with request tracking, redaction, workflow and reporting.
- Incident & investigation management
- Configurable investigative case workflows and document/task management; not a dedicated industrial safety or EHS module.
Compare within Freedom of information & public access
- FOIAXpress On-PremisePublic-records request management with intake, redaction and fulfillment in a documented on-premise deployment option.
- Azure
- FormKiQ Freedom of Information and Public Access Management Directory PublisherManage FOIA and ATI request intake, triage, review, redaction, and response with deadline tracking and defensible redaction documentation.
- AWS
- Limina DEID ContainerCommercial containerized de-identification engine for sensitive text and document processing.
- AWS
- Philter by Philterd (Self-Hosted / Cloud Marketplace)Open-source API that identifies and redacts sensitive information in text and PDFs.
- AWS
- Azure
- Google Cloud
- Reveal Enterprise Private DeploymentCustomer-operated review and e-discovery platform with redaction, audit and production workflows.
- AWS
- Azure
- Tonic TextualCommercial self-hosted text and document de-identification software installed with an official Helm chart.
- AWS
- VIDIZMO Digital Evidence ManagementCommercial digital-evidence and redaction platform with customer-account AWS and Azure deployments.
- AWS
- Azure
These products address related workflows; read their category-fit notes before comparing scope. See all of Freedom of information & public access →
Installation outline
- Choose the documented deployment option and a dedicated cloud environment. Follow the launch methodology.
- Review the vendor's installation documentation, required permissions and outbound data flows.
- Deploy to a non-production environment; configure identity, networking and monitoring.
- Test backup recovery and upgrades before promoting to production.
Evidence trail
Every claim on this page traces to the sources below. They document the deployment option; they do not constitute a security certification.
- Deployment sourcesChecked
- Enterprise capabilities and physical/virtual on-premises deployment ↗www.arkcase.com
- FOIA solution ↗www.arkcase.com
- Current solution guide, deployment and licensing ↗www.arkcase.com
- Edition and license pricing ↗www.arkcase.com
- 2026 maintenance ↗www.arkcase.com
- Cloud deployment evidenceChecked
The linked sources describe each deployment path, edition and support scope. Community templates and partner statements are identified in the notes.
- ArkCase vendor-maintained Helm deployment tested on EKS ↗ · AWS
Vendor / upstream documentation · Reviewed 2026-11-12. Vendor support commitment: not assessed; confirm the selected release and contract.
The vendor Helm repository explicitly lists Amazon EKS among its tested Kubernetes environments. It supports licensed Enterprise or Community backing components based on supplied licenses. Confirm the ArkCase Enterprise package, component entitlements, storage, secrets and supported chart/release combination; this is a self-managed stack rather than ArkCase SaaS.
- ArkCase vendor-maintained Helm deployment tested on EKS ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked