Your cloud relationship
Keep cloud resources and consumption under your account, subscription, or Google Cloud organization, folders, and projects.
Managed BYOC • Bring your own cloud.
Your cloud. Our platform. Your final authority.
Keep your AWS GovCloud account, Azure Government subscription, or qualified Google Cloud organization and projects. Liminaid operates the agreed platform through restricted, delegated access, supporting Build developers and Control teams that retain enterprise authority.
Retain ownership without rebuilding the platform.
A consistent developer experience
Offer the same approved catalog and deployment patterns across participating teams.
Managed operations within your rules
Delegate defined platform tasks to Liminaid while retaining enterprise policies and final administrative authority.
The control plane runs inside your environment.
The Liminaid control plane is designed to run inside the qualified customer-owned environment. Reviewed templates, scoped policies, and embedded Assurance support the agreed workload boundary. Provider, service, region, support, and AI-processing eligibility are reviewed together.
Delegate operations, not unrestricted access.
Separate locally running automation from human support access. Use narrowly scoped, temporary access for authorized operations, with privileged activity logged and managed under the agreed access policy.
Platform updates and maintenance follow an agreed change process rather than an unrestricted vendor change channel.
Your environment remains yours.
You retain
Your cloud account, subscription, or Google Cloud resource hierarchy; applications and data; cloud billing; enterprise identity policies; encryption controls; and final administrative authority.
Liminaid supplies
Licensed platform software, the curated catalog, reviewed deployment patterns, monitoring, evidence, and agreed managed operations.
You decide
Authoritative data classifications, permitted users and activities, necessary authorizations, and customer application requirements.
Cloud ownership does not make every resource part of Liminaid’s managed scope. The operating agreement identifies managed resources, controls, evidence, and responsibilities. Independently operated resources can receive separately scoped standalone Assurance coverage.
Keep a credible operational exit path.
Customer-accessible configurations, documentation, backups, and evidence support continued ownership. Revoking optional Liminaid human access should not delete resources or deliberately stop locally running workloads.
Build on your cloud. Keep your operating authority.
Build and Control, in your environment
Build supports developers using qualified services and deployment templates. Control supports mature teams integrating approved API, infrastructure-as-code, identity, and release workflows. Specific integrations are qualified during architecture review.
Assurance with an explicit boundary
Embedded Assurance is designed to investigate access and configuration changes, identify gaps, and verify corrections within your managed PaaS scope. Separately authorized existing resources can be assessed without transferring their operations to Liminaid.
Explore standalone Assurance →Connector permissions, evidence custody, approved AI processing, and consequential-change approvals are agreed for each covered environment. The assessment scope is not the same as the cloud ownership boundary.
Discuss assessment of independently operated resources →Questions
Can our administrators retain final control?
Yes. The customer retains final administrative authority. The agreed operating model must identify which controls Liminaid manages and how customer changes affect monitoring and assurance.
How is this different from Private Edition?
Liminaid performs agreed day-to-day platform operations in Managed BYOC. In Private Edition, your personnel perform those operations.
Does bringing our own account change the service catalog?
The core platform approach remains the same. Specific services and configurations are selected for the customer's provider, workload, and approved boundary.
Keep your cloud. Add a controlled platform.
Discuss the account ownership, operational support, and workload requirements your enterprise needs to preserve.
