Ready: use the application
Managed cloud and AI applications with guided onboarding, approved sources, and agreed operational support. You do not need to build an application to start the conversation.
Explore Ready →Start with how your team works.
Build: develop on an approved foundation
Create your own application using qualified runtime, data, and AI services, reviewed templates, and defined deployment workflows.
Explore Build →Control: integrate your platform
Keep your toolchain and operational authority while integrating qualified platform patterns, policy interfaces, and evidence into mature workflows.
Explore Control →Already have the infrastructure you need? Explore standalone Liminaid Assurance without a PaaS purchase.
Who owns the environment? Who operates the platform?
These three PaaS models define infrastructure ownership and day-to-day operations, independently of Ready, Build, or Control. Embedded Assurance covers the agreed platform scope; standalone Assurance is a separate path for existing infrastructure.
Managed Platform
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 →Managed BYOC
Liminaid operates the agreed platform inside your AWS GovCloud account, Azure Government subscription, or qualified Google Cloud organization and projects through 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 →Private Edition
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 →Approved building blocks, ready for your workload.
The catalog is designed around reviewed, versioned configurations for application, data, platform, and AI services. Each selection is qualified for its provider, region, workload profile, and operating model. Discuss current service coverage for AWS GovCloud, Azure Government, or qualified Google Cloud configurations.
Application services
Application runtimes and containerized workloads deployed through reviewed patterns.
Data services
Storage and databases with approved access and supporting configurations.
Platform foundations
Networking, secrets, logging, backup, and recovery capabilities appropriate to the environment.
AI services
Document retrieval, approved model endpoints, and supporting components for controlled AI use cases.
Discuss Your Service Requirements →Keep the operating boundary active.
Customer-approved export-control restrictions, CUI safeguards, cybersecurity requirements, and program obligations guide deployment, access, and information movement. Preventive controls act where authorized and technically possible; observable changes feed ongoing Assurance.
Access
Apply approved personnel eligibility, project authorization, and workload permissions.
Deployment
Use reviewed templates and identify changes outside the approved configuration.
Connections
Restrict unapproved network paths and external services within the managed scope.
AI processing
Govern source access, retrieval, model endpoints, tools, outputs, and logs.
Operations
Align maintenance, privileged access, monitoring, and recovery with the selected offering.
Evidence
Preserve records of configuration, access, deployment, policy enforcement, and change.
A clearer path to production.
1. Define the workload.
Identify the application or AI use case, required services, authorized users, and customer-approved restrictions.
2. Select the operating model.
Decide whether Liminaid or your organization owns and operates the environment.
3. Deploy through approved patterns.
Provision the catalog services and apply the agreed access, deployment, and connectivity policies.
4. Maintain the boundary.
Operate the platform, review changes, and preserve evidence under the agreed responsibility model.
Assurance continues after deployment.
Embedded in your agreed platform scope
Liminaid Assurance is designed for 24/7/365 event-driven and scheduled checks. AI agents connect access and configuration changes to their context, investigate gaps, and prepare recommendations. Defined technical tests verify results and preserve usable evidence.
The operator and approval process follow Managed Platform, Managed BYOC, or Private Edition. Coverage depends on qualified services and observable telemetry, not an assumption that every resource is monitored.
Independent of a platform migration
Standalone Assurance connects authorized existing infrastructure, including resources outside a Liminaid-managed scope. Read-only observation is the default; changes require separately approved authority. Coverage already included in your PaaS scope does not require a second standalone subscription.
Explore Liminaid Assurance →AWS GovCloud, Azure Government, and qualified Google Cloud configurations are evaluated by provider, service, region, workload, and operating arrangement. Applicable ITAR, EAR, NIST SP 800-171, DFARS, and CMMC mappings support defined technical controls, not blanket certification.
Understand qualification and responsibilities →Know what the platform covers.
Does selecting government cloud make every workload compliant?
No. Liminaid supports a defined operating environment and customer-approved controls. Classification, permitted recipients and activities, and required export authorizations remain customer responsibilities.
Can we use any cloud service or AI model?
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.
Can we retain our own cloud account?
Yes. Managed BYOC and Private Edition are designed for customer-owned environments. The difference is who performs day-to-day platform operations.
Do you support classified workloads?
Liminaid’s described scope is sensitive, unclassified cloud and AI workloads, including customer-approved export-control, CUI, and program-specific requirements. Classified-system support is not included.
