{"slug": "elastic-announces-ga-of-cross-project-search-on-serverless-enabling-teams-to-all", "title": "Elastic announces GA of cross-project search on Serverless, enabling teams to query across all linked projects without moving a byte", "summary": "Elastic announced the general availability of cross-project search (CPS) for Elastic Cloud Serverless, letting organizations run a single query across multiple serverless projects without moving data. The GA release supports up to 100 linked projects by default and follows the tech preview launched on April 16, 2026; Elastic said cross-cluster search, the comparable feature in Elastic Cloud Hosted, is already used by more than 80% of large ECH customers, some managing over 50 remote cluster connections on a single deployment. CPS queries data in place across regions, project types, and cloud providers, supporting Observability, Security, Search, and vector database workloads.", "body_md": "# Elastic announces GA of cross-project search on Serverless, enabling teams to query across all linked projects without moving a byte\n\nElastic today announced the general availability of cross-project search (CPS) for Elastic Cloud Serverless, enabling organizations to run a single query across multiple serverless projects. With CPS, customers can search across all regions, project types, and cloud providers, with easy setup, versionless compatibility, and complete security scope. Data is queried in place, eliminating data movement risk and keeping egress costs minimal. It supports all solutions, including Observability, Security, Search, and vector database workloads, giving teams centralized visibility without the operational overhead of centralizing data.\n\nOrganizations manage data across projects for legitimate reasons: data residency compliance, tenant data isolation, or organizational structure needs. But it can create a painful side effect: no unified visibility. SOC teams jump between regional projects chasing a threat. Site reliability engineers (SREs) can't see production and staging signals in one place. The workaround, centralizing data, means storing and moving the same bytes twice, and risking sovereignty violations. Existing solutions don't help either; some are locked to a single cloud vendor, while others require version coordination and server setup just to run a federated query.\n\nCPS truly breaks down data silos across distributed architectures without compromising data isolation, residency, or boundaries that systems rely on. By delivering transparently merged results in a single query, CPS allows teams to analyze cross-departmental security signals side by side or seamlessly correlate production and staging logs, or developing search apps with context from multiple linked projects, all without forcing separate deployments into a single environment.\n\nCross-cluster search ([CCS](https://www.elastic.co/docs/explore-analyze/cross-cluster-search)), a similar feature in Elastic Cloud Hosted (ECH), a fully managed cloud service for running the Elastic Stack, is already used by more than 80% of large ECH customers with complex architectures, some managing over 50 remote cluster connections on a single deployment. CPS delivers the same capability on Serverless without the need to understand deployment topology, configure certificates, or per-connection authentication. CPS infrastructure is abstracted by design: three clicks in the Cloud console to link projects, with authentication handled at the org level by Elastic's control plane. \n\nThat is the entire setup needed, period.\n\nOnce linked, searches in Discover, ES|QL, dashboards, and alerting rules run across all linked projects automatically, with the Kibana CPS Scope Picker keeping scope firmly under your control.\n\n## CPS: The Serverless-native approach\n\nHere’s how it works: From your project settings, select the projects you want to link. Filters and tags help target the right environments. Once saved, searches in Discover, dashboards, and alerting automatically include data from every linked project.\n\nSimple setup:\n\nLinked projects data is queried in Discover by default.\n\nThe CPS scope selector in Kibana lets analysts and engineers switch query scope without changing query syntax — filtered by project tags or just the current one.\n\nAdministrators set the default per Kibana space. A space used for local incident investigation restricts default scope to a single project; a global operations space defaults to the full linked set. Users can override the default for any individual query or session using the project picker, without touching the space configuration.\n\n## What’s new in general availability?\n\n[CPS launched in tech preview](https://www.elastic.co/blog/cross-project-search-serverless-tech-preview) on April 16, 2026. This GA release ships with meaningful additions. \n\n**Scale:** Support for up to 100 linked projects is included by default. Enterprise teams and MSSPs that link per-client or per-region projects can now operate at the scale their architectures require. Higher limits are available upon request. \n\n**Serverless project as an origin:** At GA, existing projects can link and query across as many as 100 linked projects without requiring migration or recreation. \n\n**ML and AI capabilities:** With CPS, Elastic ML jobs detect anomalies in time-series data unsupervised, and at GA they can query across multiple linked projects in a single job. Application performance monitoring (APM) anomaly detection in Elastic Observability can also span linked projects, giving SRE teams a unified anomaly view. Moreover, Elastic Agent Builder enables AI agents across all solutions to retrieve context from multiple linked serverless projects, establishing CPS as a foundational building block for production agents operating on distributed data.\n\n**Versionless and cloud-agnostic:** Teams aren't locked into a single cloud vendor or forced to coordinate versions across deployments just to do a search. And it works across every solution: Observability, Security, Search, and vector database workloads.\n\n- **Observability:** Application and infrastructure monitoring, alerting, SLOs, and APM anomaly detection work across linked projects enabling flexible data locality and analysis.\n- **Security:** CPS powers the Central SOC model: Detection rules run once on a central project and query across every linked project, so SOC teams triage one alert without manually merging data or duplicating alert rules. Entity information and Elastic Defend telemetry from linked projects feed that same central view.\n- **Search:** ES|QL queries and Discover sessions span linked projects by default. Across all solutions at GA an AI agent can retrieve context from multiple linked projects in a single query, making CPS a foundational building block for production agents that operate across distributed data.\n\n**Complete access control:** A user's access to data across linked projects is determined by their individual permissions on each project, not by where they're querying from.  What that user can see is always complete and consistent with what they are authorized to see.\n\n**Reduced costs:** Because data stays where it is, you pay for the queries you run, not for storing and moving the same bytes twice.\n\n**Full project routing:** It gives teams precise control over which projects a query targets. Using predefined tags such as region, cloud provider, and project alias — or custom tags you define — you can route any query to a specific subset of linked projects. Named expressions and boolean logic (AND, OR, NOT) let you build reusable routing rules for common patterns, such as \"all EU projects\" or \"all MSSP tenant environments except staging.\"\n\n**Programmatic CPS access:** CPS has introduced a new user role that enables anyone, not just organization owners, to generate Cloud API keys for CPS queries, removing friction for teams building pipelines and applications on CPS.\n\n## Frequently asked questions\n\n**What is CPS in Elastic Cloud Serverless?** CPS lets you run a single query across multiple Elastic Cloud Serverless projects from Discover, dashboards, or alerting. Results are merged transparently. Setup takes minutes from your project settings.\n\n**How is CPS different from CCS?** CCS is the equivalent feature in \n\n[Elastic Cloud Hosted](https://www.elastic.co/cloud). CCS requires mapping your deployment architecture, managing API keys or certificates per remote connection, and referencing remote cluster names in queries. CPS handles authentication and topology automatically — link projects in the UI, and searches span all of them by default.\n\n**How much does CPS cost?** CPS has two pricing dimensions. Mounted data is charged at $0.009 per GB retained in linked projects per month (pricing varies by project types, region and cloud service provider). Data egress out is charged at $0.05 per GB — the same rate as standard non-CPS egress, tracked on a separate line item so you can see exactly what CPS queries are contributing to your transfer costs. A team ingesting 10 GB per day with 30-day retention and one linked project adds approximately $4.50 per month in mounted data costs, plus egress based on query volume — typically a small fraction of total CPS cost for common single-pane-of-glass usage.\n\n**Which project types and tiers include CPS?** CPS is available on all serverless project types. For Observability and Security projects, the Complete tier is required.\n\n**Can I control which projects are included in a search?** Yes, at both the UI and query level. In Kibana, the project picker lets users switch between all linked projects and just the current one without changing query syntax; administrators set per-space defaults to control the scope for each team or workflow. At the query level, project routing parameters in ES|QL and the search API let you target specific linked projects directly, without going through the UI.\n\n## Get started\n\nIf you are already running Elastic Cloud Serverless, CPS is available in your project settings today. Link your projects, open Discover, and run your first cross-project query.\n\nNot yet on Elastic Cloud Serverless? [Sign up for free!](https://cloud.elastic.co/registration?page=docs&placement=docs-siderail)\n\n*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.*", "url": "https://wpnews.pro/news/elastic-announces-ga-of-cross-project-search-on-serverless-enabling-teams-to-all", "canonical_source": "https://www.elastic.co/blog/cross-project-search-elastic-serverless-ga", "published_at": "2026-09-16 00:00:00+00:00", "updated_at": "2026-09-16 15:11:15.267082+00:00", "lang": "en", "topics": ["ai-infrastructure", "ai-tools", "developer-tools"], "entities": ["Elastic", "Elastic Cloud Serverless", "cross-project search", "cross-cluster search", "Elastic Cloud Hosted", "Elastic Stack", "Kibana", "Discover"], "alternates": {"html": "https://wpnews.pro/news/elastic-announces-ga-of-cross-project-search-on-serverless-enabling-teams-to-all", "markdown": "https://wpnews.pro/news/elastic-announces-ga-of-cross-project-search-on-serverless-enabling-teams-to-all.md", "text": "https://wpnews.pro/news/elastic-announces-ga-of-cross-project-search-on-serverless-enabling-teams-to-all.txt", "jsonld": "https://wpnews.pro/news/elastic-announces-ga-of-cross-project-search-on-serverless-enabling-teams-to-all.jsonld"}}