elastic / elastic/roadmap

Multi-tenant management for Elastic Cloud

Open
#232 0 comments 0 reactions 1 assignee Claimed by @alxchalkias View on GitHub
Component: Elastic Cloud Hosted Component: Elastic Cloud Serverless product-area:platform
Dominant language
No language data
Stars
6
Forks
1
PR merge metrics
No merged PRs in 30d

Description

**What the feature is**

Multi-tenant management for Elastic Cloud

A way for enterprises, managed service providers (MSPs), and MSSPs to centrally manage multiple isolated Elastic Cloud environments from a single account. Each tenant gets a full Elastic Cloud experience with strong security boundaries, while administrators gain centralized oversight, billing visibility, and governance controls.

**Value proposition**

Today, customers who manage multiple teams or serve multiple end-customers must choose between separate Elastic Cloud organizations (losing centralized management) or a single shared organization (sacrificing isolation). This feature removes that trade-off by introducing a management hierarchy that combines tenant isolation with centralized administration and billing.

**Expected outcome**

Administrators can create and manage tenant environments, view consolidated billing across tenants, and enforce governance policies — all from a central management view. Tenant users operate in a standard, isolated Elastic Cloud experience.

**Key user stories / use cases**

- An MSP creates isolated environments for each of their customers, with centralized billing and per-customer usage visibility for chargeback.
- A large enterprise provides each business unit with its own Elastic Cloud environment while maintaining central security policies and cost oversight.
- A tenant administrator manages their own users, configurations, and resources without seeing other tenants or the parent organization.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.