Limina DEID Container
Commercial containerized de-identification engine for sensitive text and document processing.
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
CloudFormation; Helm / Kubernetes operator; Kubernetes manifests
Runs in
Documented customer environment
Customer EKS Helm deployment or AWS ECS CloudFormation stack running licensed CPU or GPU containers.
- AWS: Customer cloud account
- AWS
Servers / containers
Operated by
Your team
Customer operates the application and its cloud resources, including secrets, backups, monitoring and upgrades. Review any support access and configured external services; preserve application data, configuration and keys for migration or exit.
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.
AWS EKS Guide ↗ · Source checked 2026-11-19
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 | CloudFormation; Helm / Kubernetes operator; Kubernetes manifests |
|---|---|
| Infrastructure | Servers / containers Customer EKS Helm deployment or AWS ECS CloudFormation stack running licensed CPU or GPU containers. Persistent application containers and VMs are classified as servers even when the provider manages their infrastructure. |
| Licensing model | Commercial Only Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. |
| License | Commercial proprietary licence; product, user, database and support entitlements must be agreed for the selected installation. |
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
Not confirmedEvidence and scope for Single sign-on
The reviewed container deployment documentation establishes deployment/cluster access and API-oriented processing, but does not establish external SAML/OIDC user sign-in for the DEID container itself. AWS IAM/EKS identity and a separately hosted customer portal are not proof of application-user federation.
Limina self-hosted DEID container user/authentication surface; hosted API and portal capabilities are not transferred · Source ↗ · Reviewed 2026-11-20
Sources checked — unresolved · Editor reviewed.
- Deployment artifact / IaC
DocumentedEvidence and scope for Deployment artifact / IaC
Limina publishes nested CloudFormation templates to provision an EC2-backed ECS cluster, networking, bastion and the CPU container. The guide describes a prototyping starting point and production guide, not production validation. GPU use needs AMI, ECS agent and task changes; changing only the image tag is insufficient.
Limina CPU-container AWS ECS template; review nested files, IAM, secrets, capacity and selected container entitlement · Source ↗ · Deployment artifact ↗ (main.yaml at an unversioned S3 URL; retain/pin the reviewed parent and nested templates) · Reviewed 2026-11-20
Documented · Editor reviewed.
- Minimum footprint / sizing
DocumentedEvidence and scope for Minimum footprint / sizing
The EKS guide calls for worker memory greater than 16 GB; the GPU variant also needs a GPU-enabled node image and more than 30 GB disk. It recommends a larger instance such as m5zn.3xlarge for image/PDF processing. These are deployment recommendations, not a complete model/concurrency or HA capacity guarantee.
Limina EKS worker guidance; select CPU/GPU container, models, storage and replica capacity for the actual workload · Source ↗ · Reviewed 2026-11-20
Documented · Editor reviewed.
- License pricing
Not confirmedEvidence and scope for License pricing
The public website Terms of Use do not establish the self-hosted DEID container’s commercial licence, price or support rights; obtain the applicable software agreement.
Selected self-hosted commercial product; contract confirmation remains necessary · Source ↗ · Reviewed 2026-11-19
Sources checked — unresolved · 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
Formerly Private AI. The automated ECS stack is a prototyping starting point and production guide, with capacity and security review required. Website terms do not substitute for the applicable container licence/order. Redaction output still needs disclosure-policy and accuracy review.
Category fit
- Freedom of information & public access
- Commercial containerized de-identification engine for sensitive text and document processing.
- Document management
- Commercial containerized de-identification engine for sensitive text and document processing.
Compare within Freedom of information & public access
- ArkCase Enterprise (self-managed)Configurable case management platform with FOIA and investigative solutions.
- AWS
- 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
- 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
- AWS EKS Guide ↗docs.getlimina.ai
- AWS ECS CloudFormation ↗docs.getlimina.ai
- Terms of Use ↗www.getlimina.ai
- OpenAPI v4.5.2 ↗docs.getlimina.ai
- GitHub Org ↗github.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.
- AWS EKS Guide ↗ · AWS
Vendor / upstream documentation · Reviewed 2026-11-19. Vendor support commitment: not assessed; confirm the selected release and contract.
Customer EKS Helm deployment or AWS ECS CloudFormation stack running licensed CPU or GPU containers. Formerly Private AI. The automated ECS stack is a prototyping starting point and production guide, with capacity and security review required. Website terms do not substitute for the applicable container licence/order. Redaction output still needs disclosure-policy and accuracy review.
- AWS EKS Guide ↗ · AWS
- Infrastructure evidenceChecked
- Licensing evidenceChecked