Liminaid Platforms.
Give your teams a self-service catalog for applications, data, and AI. Choose a Liminaid-managed environment, managed operations inside your own cloud account, or a private platform operated by your team.
The three ownership and operating models over a common service catalog.
Start with the control your organization requires. Each offering uses the same core platform approach, with different responsibilities for ownership and operations.
Liminaid provides and operates the cloud environment, platform software, service catalog, and agreed operational services.
Environment: Provided by Liminaid.
Routine platform operations: Liminaid.
Best fit: Teams that want the most fully managed experience and do not require their own underlying cloud account.
Explore Managed Platform →Liminaid deploys and operates the platform inside your AWS GovCloud account or Azure Government subscription under restricted, delegated access.
Environment: Customer-owned.
Routine platform operations: Liminaid within the agreed scope.
Best fit: Enterprises that require cloud ownership while outsourcing platform operations.
Explore Managed BYOC →Your team operates Liminaid inside your environment. Liminaid supplies the software, catalog, supported releases, and support model.
Environment: Customer-owned.
Routine platform operations: Customer.
Best fit: Organizations that require operational custody and no standing vendor human administration.
Explore Private Edition →Use a curated, versioned catalog rather than unrestricted access to every cloud service. The available configuration is defined around the workload and the customer's approved boundary.
Application runtimes and containerized workloads deployed through reviewed patterns.
Storage and databases with approved access and supporting configurations.
Networking, secrets, logging, backup, and recovery capabilities appropriate to the environment.
Document retrieval, approved model endpoints, and supporting components for controlled AI use cases.
Discuss Your Service Requirements →Conceptual catalog grouped into Applications, Data, Platform Foundations, and AI.
Customer-approved requirements guide what may be deployed, who may access it, and where information may move.
Apply approved personnel eligibility, project authorization, and workload permissions.
Use reviewed templates and identify changes outside the approved configuration.
Restrict unapproved network paths and external services within the managed scope.
Govern source access, retrieval, model endpoints, tools, outputs, and logs.
Align maintenance, privileged access, monitoring, and recovery with the selected offering.
Preserve records of configuration, access, deployment, policy enforcement, and change.
Define the workload → select the operating model → deploy through approved patterns → maintain the boundary.
Identify the application or AI use case, required services, authorized users, and customer-approved restrictions.
Decide whether Liminaid or your organization owns and operates the environment.
Provision the catalog services and apply the agreed access, deployment, and connectivity policies.
Operate the platform, review changes, and preserve evidence under the agreed responsibility model.
No. Liminaid supports a defined operating environment and customer-approved controls. Classification, permitted recipients and activities, and required export authorizations remain customer responsibilities.
The platform uses a curated catalog. Service and model choices must fit the approved workload configuration; the catalog is not a promise of unrestricted service availability.
Yes. Managed BYOC and Private Edition are designed for customer-owned environments. The difference is who performs day-to-day platform operations.
The platform scope described here is unclassified workloads involving export-controlled technical data. This page does not claim classified-system support.
© 2026 Liminaid. All rights reserved.
