Cosmic Wire · 3 Nov 2026 · Som Raghavan

Localised enterprise LLM viability

From the canonical brief: commercially viable as a sovereignty-led offer for a narrow set of enterprises — not as a broad cost-saving play, and not differentiated from Palantir on architecture alone.

Source Cosmic Wire localised enterprise LLM viability analysis.docx Scope Viability only For Keli / Mark iterate

Preliminary conclusion

Where it works Hard legal/contract boundary; high-volume device/sensor data at the edge; or more than roughly $1.7M/yr of public-model spend on work a local model can handle (central case). Markets where vendors offer storage residency but not in-region processing are a plausible opening.
Where it does not Most orgs’ AI use is too small or bursty to cover a fully loaded local deployment of about $0.6M–$2.0M/yr. No-training defaults, ZDR, regional storage and customer-managed keys already satisfy many US/EU buyers.
Vs Palantir Palantir already lets customers self-host models inside AIP with no extra platform fee. Cosmic’s edge, if any — device-level intelligence, ingestion/compression at source, volumetric data — is currently unproven.

Pricing shape: layered, not per-token — platform subscription, infrastructure at visible cost-plus, bundled public-model allowance with pass-through overage, security/monitoring where sovereignty drives the sale, short paid POC. Pike already follows this shape.

Assumptions that drive the conclusion (by weight): (1) share of spend that moves local — easiest work is cheapest publicly; (2) fully loaded local cost (staff + GPU utilisation); (3) price direction — frontier mid/small cuts vs rising GPU rental; (4) hard processing boundary; (5) who operates the environment and under which jurisdiction.

Offload percentages in this analysis are illustrative sensitivity scenarios, not Cosmic forecasts or observed performance. This is not a vertical ranking, GTM plan, or final pricing recommendation.

1. Market need and current behaviour

Enterprises buy public AI mainly as seat-priced copilots and metered model APIs, and they overwhelmingly choose closed frontier models. Sensitive data does leak into AI tools, but the main exposure runs through unmanaged personal accounts, not sanctioned enterprise contracts.

Menlo Ventures (2025): ~$37B enterprise genAI spend; ~$12.5B foundation APIs; ~$7.2B copilots; 76% of use cases bought rather than built. Anthropic / OpenAI / Google hold ~88% of enterprise LLM API usage; open-source share fell from 19% to 11%.

Netskope (2026): heavy sensitive-data incidents into AI apps; ~47% of genAI users still on personal unmanaged accounts. Cost predictability is also shifting as seats turn into meters for agentic use.

Implication: evidence supports “enterprises send sensitive data to public AI.” It does not support “they do not know a local option exists.” Open-weight usage is falling while enterprises block tools. Cosmic must overcome a judgment that local is weaker and harder to run — not an information gap.

2. Potential displacement of public-model usage

Narrow, repetitive, data-sensitive work can move local with little quality loss. Frontier coding, long-horizon agents and novel reasoning cannot — and that is where spend is concentrating.

Epoch AI: best open-weight models trail closed frontier by ~4 months / 8 capability points (since Jan 2026). Strongest open models need large GPU clusters; workstation-class models score lower. Hard research-math tests still show frontier ahead.

Routing literature (e.g. LMSYS RouteLLM) shows large savings when easy tasks leave the frontier — but that is share of calls, not share of spend. The easiest work is also the cheapest publicly, so spend displacement is smaller than token displacement.

3. Net usage and economic effect

Public-model token use can fall while total inference rises (embeddings, routers, guards, retries, eval, agents). Demand also expands as unit cost falls. The defensible claim is slower growth in paid external usage, not lower overall AI spend.

On the brief’s illustrative fully loaded local costs (~$0.6M to ~$2.0M/yr depending on utilisation and staff), localisation saves money only above roughly $1M–$13M/yr of in-scope public-model spend — a few hundred very large users, not the broad market. Central case threshold ~$1.7M/yr at a blended ~$4/M tokens.

Keep three ledgers apart: customer price (Pike $15.275M proposal layers), Cosmic cost (blocked / fully loaded), customer value. Pike’s $1.4M AI allocation is customer price, not Cosmic provider COGS. BAIT is device/dashboard pricing. Assurant is draft.

4. Conditions for commercial viability

Attractive when the customer meets at least two conditions, and one is usually a hard constraint rather than cost:

ConditionTest
Sustained volumeIn-scope public spend above ~$1.7M/yr (central), steady not bursty
High utilisationLocal GPUs busy most of the day (idle capacity kills the case)
Local model good enoughPasses the customer’s own eval set
Hard boundaryLaw/contract/OT/jurisdiction that residency-only does not solve
Operable environmentClear who runs it and under which jurisdiction

On cost alone it clears only for the largest users. Public stays cheaper for small/bursty loads and for hard frontier work.

5. Pricing-model comparison

Do not price a localised LLM primarily per token — that invites a line-by-line fight with public prices that fall every quarter. Prefer a layered structure that prices the governed platform and passes model/infra through transparently — which is what Pike already does.

ShapeCosmic referenceFit
Platform subscriptionPike $12M; Assurant $12M draftStrong — prices the governed environment
Bundled AI allowance + overagePike $1.4M AI allocation (customer price)Strong — avoid pure token retail
Infrastructure cost-plusPike $75K host lineNeeded — brief flags $75K as likely too low for local inference compute
Security / monitoringPike $1.8MFits when sovereignty drives the sale
Per-device / active userAssurant diagnostics; BAIT $0.14/userDevice/dashboard — not LLM token economics
Paid POCBAIT 30-dayRight discovery path; users/execution unconfirmed

6. Palantir comparison

Palantir already sells local-plus-public inside a governed platform. Models are a swappable input: provider-hosted, Palantir-hosted open models, and customer self-hosted GPUs as first-class AIP models — pitched for sovereignty, air-gap and cost control, with no extra platform fee for registered models.

Value sits in integration, Ontology, governance and operational apps. Cosmic is not differentiated by “local model” alone. Any edge must be proven on device-native intelligence, ingestion/compression at source, and volumetric data — none of which are evidenced yet.

Do not sell Palantir as a thin ChatGPT wrapper.

7. Data-sovereignty value

“Not used for training” is now standard — it cannot be Cosmic’s argument. Sovereignty turns on where data is processed, under which law, who holds the keys, and who can access it. Cosmic must answer those questions about itself too.

OpenAI Business/Enterprise: no training by default, ZDR for qualifying API customers, customer-managed keys, storage residency in multiple regions. Bedrock: does not store/log prompts for training; provider models in AWS-owned accounts. For many US/EU buyers that is enough. Cosmic wins where processing location / air-gap / OT boundaries still fail under residency-only offers.

8. Evidence Cosmic still needs

Until these are evidenced, the proposition is a credible hypothesis, not a proven product:

  1. Written definition and architecture of the Relativity Engine (and how it differs from ontology / RAG / entity resolution)
  2. Local-model results on a customer’s own evaluation set + router accuracy
  3. Measured offload from a live deployment or POC (tokens and spend; total inference change)
  4. Fully loaded cost per deployment (GPUs, hosting, staff, support) — resolves the Pike hosting question
  5. Deployment and jurisdiction model (who operates, where incorporated, keys, air-gap)
  6. Device-data benchmark vs general integration tooling
  7. Paid customer signals (BAIT execution/users; Pike/Assurant status)
  8. Security credentials (SOC 2 / ISO 27001)
Gaps flagged in the brief: the “they don’t know local exists” assumption is not supported; Pike’s $75K hosting line looks too low for local inference; Assurant draft has unresolved/conflicting terms.