# Kraken Technologies

> Kraken Technologies is the UK energy-technology company behind Kraken, the licensed cloud operating system for utilities. Spun out of Octopus Energy, it says it supports more than 90 million customer accounts for licensees including E.ON Next, EDF, Origin, Tokyo Gas, National Grid, Good Energy, Plenitude, Energy Queensland, Essential Energy, Portsmouth Water and TalkTalk, across electricity, gas, water and broadband. Its integration layer, Open Kraken, is real but closed: APIs, events, Embedded Apps, Flow automation and an announced MCP-based AI access layer are all licensee-only. No base URL, endpoint list, OpenAPI, AsyncAPI or GraphQL schema is published anywhere on the public web, and docs.kraken.tech returns an SSO login page for every path — including /openapi.json, /llms.txt and /.well-known/openid-configuration.

Generated by API Evangelist (apievangelist.com) from the public Kraken Technologies surface on 2026-07-27. Kraken publishes no llms.txt of its own (/llms.txt returns 404 on www.kraken.tech and the login page on docs.kraken.tech).

Homonym warning: "Kraken" also names the Kraken cryptocurrency exchange (kraken.com) and the KrakenD API gateway (krakend.io). Neither is this company. Everything below is on kraken.tech or a GitHub org whose declared website is kraken.tech.

## APIs

- [Open Kraken APIs and Events](https://www.kraken.tech/open-kraken): The integration layer of the Kraken utility operating system — "APIs, events and MCP", plus Flow automation and Embedded Apps. No base URL, endpoint list, authentication scheme or machine-readable contract is published. Access requires a Kraken licence.
- [Open Kraken AI Access Layer (MCP)](https://www.kraken.tech/open-kraken): Announced MCP gateways that let a utility's own AI agents orchestrate approved actions across Kraken, with fair use included; "gradually released". No server URL, tool list, scope model or transport is published; mcp.kraken.tech does not resolve.

## Docs

- [Kraken Docs](https://docs.kraken.tech/): Reference documentation. SSO-gated at every path; credentials are issued to licensees and contracted partners.
- [Open Kraken](https://www.kraken.tech/open-kraken): Public description of Flow, Embedded Apps, APIs/events and the AI access layer.
- [Kraken example apps](https://github.com/kraken-tech/kraken-apps-examples): The most substantive public developer documentation Kraken publishes — the Embedded Apps initialisation contract, the Kraken App Store Proxy headers, and the app JWT/JWKS model.
- [Tako Design System](https://tako.kraken.tech/): Public documentation for Kraken's component libraries.
- [Tako React Storybook](https://tako-react-kraken-tech.vercel.app/?path=/docs/components): 50 component families, public.
- [Tako HTML Storybook](https://tako-html-kraken-tech.vercel.app/?path=/docs/components): 26 component families, public.
- [Latest updates](https://www.kraken.tech/product-updates): Periodic product roundup (no versions, no dates).
- [Marketplace](https://www.kraken.tech/marketplace): Partner and solution listings, governed by signed access-and-use terms.

## Specs

No OpenAPI, Swagger, AsyncAPI, GraphQL SDL, JSON Schema or Protobuf definition is published by Kraken Technologies anonymously. Probed 2026-07-27: docs.kraken.tech /openapi.json, /swagger.json, /api-docs, /redoc, /graphql all return the SSO login page as text/html; www.kraken.tech returns 404 for the same paths; api.kraken.tech, developer.kraken.tech, data.kraken.tech and mcp.kraken.tech do not resolve in DNS.

## Artifacts

- [apis.yml](https://raw.githubusercontent.com/api-evangelist/kraken-technologies/refs/heads/main/apis.yml): APIs.json index for Kraken Technologies.
- [Authentication](https://raw.githubusercontent.com/api-evangelist/kraken-technologies/refs/heads/main/authentication/kraken-technologies-authentication.yml): The Kraken Apps proxy JWT (JWKS at /.well-known/jwks.json, kid kraken-app-store, 25-hour tokens), docs SSO, and SAML IdP integration.
- [Conventions](https://raw.githubusercontent.com/api-evangelist/kraken-technologies/refs/heads/main/conventions/kraken-technologies-conventions.yml): The Embedded Apps initialisation arguments and the X-Kraken-App-Proxy-Destination / X-Kraken-App-Proxy-Authorization request contract.
- [Components](https://raw.githubusercontent.com/api-evangelist/kraken-technologies/refs/heads/main/components/kraken-technologies-components.yml): Tako React and Tako HTML inventories.
- [MCP](https://raw.githubusercontent.com/api-evangelist/kraken-technologies/refs/heads/main/mcp/kraken-technologies-mcp.yml): The published Tako Storybook MCP configuration and the announced Open Kraken AI access layer.
- [Packages](https://raw.githubusercontent.com/api-evangelist/kraken-technologies/refs/heads/main/packages/kraken-technologies-packages.yml): First-party open-source Python libraries; Tako packages on a private npm registry; no API client library.
- [Changelog](https://raw.githubusercontent.com/api-evangelist/kraken-technologies/refs/heads/main/changelog/kraken-technologies-changelog.yml): Tako release notes; no API changelog exists.
- [Lifecycle](https://raw.githubusercontent.com/api-evangelist/kraken-technologies/refs/heads/main/lifecycle/kraken-technologies-lifecycle.yml): No public versioning policy, deprecation policy, SLA or status page.
- [Conformance](https://raw.githubusercontent.com/api-evangelist/kraken-technologies/refs/heads/main/conformance/kraken-technologies-conformance.yml): ISO/IEC 27001:2022, SOC 1/2 Type 2, GDPR, JWT/JWKS, SAML, MCP; no energy data standard.
- [Trust Center](https://raw.githubusercontent.com/api-evangelist/kraken-technologies/refs/heads/main/security/kraken-technologies-trust-center.yml): Certifications and security architecture.
- [Vulnerability disclosure](https://raw.githubusercontent.com/api-evangelist/kraken-technologies/refs/heads/main/security/kraken-technologies-vulnerability-disclosure.yml): Public disclosure process, private HackerOne program, no bounty, 2-business-day response target.
- [Domain security](https://raw.githubusercontent.com/api-evangelist/kraken-technologies/refs/heads/main/security/kraken-technologies-domain-security.yml): TLS/HSTS/SPF/DMARC probe results.
- [Well-known](https://raw.githubusercontent.com/api-evangelist/kraken-technologies/refs/heads/main/well-known/kraken-technologies-well-known.yml): Every /.well-known/ probe and its status — nothing is served anonymously.
- [CLI](https://raw.githubusercontent.com/api-evangelist/kraken-technologies/refs/heads/main/cli/kraken-technologies-cli.yml): The public Homebrew tap and its network-gated internal tooling.

## Access

- [Request a demo](https://www.kraken.tech/): The only public entry point; there is no self-serve developer signup.
- [BPO Partner Program](https://www.kraken.tech/bpo-partner-program)
- [Marketplace access and use terms](https://www.kraken.tech/legal/marketplace-access-and-use-terms)
- [Vulnerability disclosure process](https://www.kraken.tech/vulnerability-disclosure-process)
- [Trust Center](https://www.kraken.tech/legal/trust-center)
- [Privacy notice](https://www.kraken.tech/legal/privacy-notice)
- Tako design-system npm token: email tako@kraken.tech (read-only, rotated annually).

## Optional

- [GitHub: kraken-tech](https://github.com/kraken-tech): Python/Django open-source tooling plus the Embedded Apps examples.
- [GitHub: octoenergy](https://github.com/octoenergy): The older Kraken Technologies org — xocto, public-conventions, octotools, the Homebrew tap.
- [Insights blog](https://www.kraken.tech/insights)
- [Press releases](https://www.kraken.tech/press-releases)
- [Support portal](https://support.kraken.tech/)
- Not Kraken Technologies: developer.octopus.energy is a Kraken-powered surface published by Octopus Energy under its own brand and supply licence; it is profiled separately as octopus-energy.