Introducing cross-project search in Elastic Cloud Serverless

As organizations scale, data naturally fragments. Elastic Cloud Serverless allows you to organize your data into dedicated projects whether you’re isolating team environments, separating business units, or complying with regional data residency laws. While separating workloads offers great architectural benefits, it traditionally required consolidating data whenever a unified search was needed. 

Today, we are announcing the technical preview launch of cross-project search (CPS) for Elastic Cloud Serverless. You can now instantly query distributed Elastic Cloud Serverless projects as one — maintaining native project isolation while querying your entire organization from a single pane of glass.

Getting started with cross-project search takes just a few clicks:

1. In the Elastic Cloud console, create a new project to use as your origin — the project you’ll search from.

2. Open that project, choose which other projects to link, save your configuration, and let the Elastic control plane establish the connections.

Once linking is in place, data from linked projects appears in your origin project automatically. In Kibana, use the project picker in the navigation bar to switch between All projects and This project, and save your preferred scope to a dashboard, rule, or Discover session when you want it to stick. 

CPS gives you immediate global visibility; from your origin project, one query spans all linked projects by default. Then, when you need precision, you can narrow scope per request, per workflow, or per team default without changing where data lives.

• Route to exactly the projects you want using project_routing expressions in ES|QL queries (SET project_routing), search APIs, and any CPS-enabled endpoint. In Kibana, use the project picker in the navigation bar to switch between All projects and This project. After the tech preview release, more granular controls will be released to select subsets of projects based on criteria like the project region, cloud provider, or any custom project tags defined by your team.

• Analyze and aggregate data by linked projects using project tags in your queries. You can group results by region, environment, or team, so patterns become obvious fast without moving or duplicating data.

• Set the right default per Kibana space. Kibana spaces let each team start from the right default view of linked data. Configure a space-level default project scope (e.g., This project) so that dashboards, rules, and daily workflows open in the right slice by default, and analysts can still expand scope when needed.

The release and timing of any features or functionality described in this post remain at Elastic's sole discretion. Any features or functionality not currently available may not be delivered on time or at all.