Softwr

Developer Tools · head to head

Cortex vs Poolside

Cortex logo

Cortex

Developer Tools

Internal developer portal that scores service ownership and maturity rather than just cataloguing services

From
On request
Free plan
No
Poolside logo

Poolside

AI

Open-weight foundation models built for agentic software engineering

From
$0.06/month
Free plan
No

The short version

  • Poolside starts at $0.06/mo; Cortex prices on request.
  • Only Cortex lists service catalogue; only Poolside lists laguna S 2.1.
  • Where Poolside falls short: no self-serve public application; access is largely through enterprise sales or third-party model gateways.
  • Prices and features on this page were last checked on 31 August 2026.

Where they differ

Only the attributes on which Cortex and Poolside actually diverge.

Attributes where Cortex and Poolside differ
AttributeCortexPoolside
Starting priceOn request$0.06/month
Pricing modelQuoteUsage-based
PlatformsWeb, APIWeb, API, macOS, Windows, Linux
CategoryDeveloper ToolsAI

Identical on both: free tier (No).

Not yet recorded: founded for Cortex.

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Cortex

  • Service catalogue
  • Scorecards
  • Initiatives
  • Self-service templates
  • Query language
  • Eng intelligence
  • Integrations layer
  • On-call and ownership mapping

Only in Poolside

  • Laguna S 2.1
  • Laguna XS 2.1
  • Desktop and CLI tools
  • Open-weight models
  • Third-party gateway access

What people use each for

The jobs each tool is most often brought in to do.

Cortex

  • A platform team that needs to prove to leadership how far a Kubernetes or framework migration has actually progressed across hundreds of servicesnot Poolside
  • An organisation where ownership of production services is genuinely unknown after reorganisations or acquisitionsnot Poolside
  • Enforcing production readiness standards on new services at creation time rather than at incident reviewnot Poolside
  • Replacing a self-hosted Backstage that is consuming a full-time engineer or two just to stay upgradednot Poolside

Poolside

  • Enterprises deploying AI coding assistance across large developer organizationsnot Cortex
  • Government and defense agencies needing on-premise or sovereign coding modelsnot Cortex
  • Teams building custom coding agents on open-weight foundation modelsnot Cortex
  • Organizations wanting on-device lightweight coding modelsnot Cortex

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Cortex

  • Pricing is quote only, so a platform team cannot build a business case or compare against the true cost of self-hosted Backstage without entering a sales cycle first
  • The catalogue is only as accurate as the metadata you supply, so an organisation with inconsistent repository conventions spends its first quarter cleaning data before any scorecard means anything
  • Scorecards create political friction: publishing a per-team grade turns an engineering standard into a performance metric, and teams will game the rules rather than fix the underlying issue
  • It is closed source and hosted, so organisations with strict data residency or air-gap requirements have limited options compared with running Backstage themselves
  • Value scales with organisation size, so a company with fifty engineers and thirty services will find the catalogue tells them nothing they did not already know while still paying an enterprise contract

Poolside

  • No self-serve public application; access is largely through enterprise sales or third-party model gateways
  • Pricing for the flagship enterprise and government offering is not public and requires a sales conversation
  • Targets organizations with large (5,000+) developer headcounts, making it a poor fit for individuals or small teams
  • Documentation and product surface area are thin compared to consumer-facing coding assistants

Pricing, plan by plan

Cortex

On request
  • CortexOn request
    • Service catalogue and ownership mapping
    • Scorecards and initiatives
    • Self-service templates

Poolside

$0.06/month
  • Laguna XS 2.1On request
    • $0.06 per 1M input tokens
    • $0.12 per 1M output tokens
    • Available via OpenRouter and Vercel AI Gateway
  • Laguna S 2.1On request
    • $0.10 per 1M input tokens
    • $0.20 per 1M output tokens
    • 1M token context window
  • Enterprise / GovernmentOn request
    • Custom contracts for large engineering organizations
    • Sales-quoted pricing
    • On-premise or dedicated deployment options

Which should you pick?

Choose Cortex if

  • You need service catalogue.
  • You work on Web, API.
  • You also want scorecards.

Choose Poolside if

  • You need laguna s 2.1.
  • You work on Web, API, macOS, Windows, Linux.
  • You also want laguna xs 2.1.

Questions people ask

Is Cortex or Poolside better?
Neither clearly leads. Cortex starts at On request and Poolside at $0.06/month, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Cortex or Poolside?
Cortex starts at On request and Poolside at $0.06/month.
Does Cortex or Poolside run on more platforms?
Cortex runs on Web, API. Poolside runs on Web, API, macOS, Windows, Linux.
What is Cortex best used for?
Cortex is most often used for a platform team that needs to prove to leadership how far a kubernetes or framework migration has actually progressed across hundreds of services, an organisation where ownership of production services is genuinely unknown after reorganisations or acquisitions, enforcing production readiness standards on new services at creation time rather than at incident review, replacing a self-hosted backstage that is consuming a full-time engineer or two just to stay upgraded. Of those, a platform team that needs to prove to leadership how far a kubernetes or framework migration has actually progressed across hundreds of services and an organisation where ownership of production services is genuinely unknown after reorganisations or acquisitions are not what Poolside is typically brought in for.
What can Cortex do that Poolside cannot?
Cortex covers Service catalogue, Scorecards, Initiatives, Self-service templates. Poolside covers Laguna S 2.1, Laguna XS 2.1, Desktop and CLI tools, Open-weight models.

Answered from the vendors’ own pages

Cortex: How is Cortex different from Backstage?

Backstage is an open source framework you build and staff. Cortex is a hosted product with scorecards and initiatives out of the box and no platform team required to keep it running.

Poolside: How is Poolside's Laguna model usage priced?

Laguna XS 2.1 is priced at $0.06 per 1M input tokens and $0.12 per 1M output tokens; Laguna S 2.1 is $0.10 per 1M input tokens and $0.20 per 1M output tokens.

Source
Cortex: Is pricing published?

No. Cortex requires a sales conversation and prepares a custom proposal.

Poolside: Where can I access Poolside's models?

Laguna models are available through third-party gateways OpenRouter and Vercel AI Gateway, as well as via Poolside's own desktop and CLI tools.

Source
Cortex: Can it self-host?

It is offered as a hosted product; on-premise arrangements are handled through sales rather than published.

Poolside: Does Poolside offer enterprise or government pricing?

Yes, Poolside offers custom, sales-quoted contracts for large enterprises and government/defense customers, including on-premise or dedicated deployment options.

Source
Cortex: What is the main adoption risk?

Bad or missing service metadata. The catalogue and every scorecard on top of it inherit whatever quality your repositories already have.

Poolside: How do I get started building with Poolside's models?

Poolside's documentation provides a quickstart guide for installing the `pool` CLI and running an agent task, alongside API documentation for custom integrations.

Source
Share

Related pages

Other head to heads