Need help with your APIs? I offer API discovery, governance & evangelism services. Explore services →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC
evroc website screenshot

evroc

evroc is a European sovereign cloud provider headquartered in Stockholm, Sweden, building cloud infrastructure for the AI era for organizations that require the highest level of data security and European data residency. Its platform spans Compute (virtual machines, disks, snapshots, placement groups), Networking (VPCs, subnets, public IPs, security groups, IPv6, load balancers), Storage (S3-compatible object storage and file store), IAM (organizations, projects, service accounts, and a fine-grained RoleBindings permission system), Quotas, and Think (shared and dedicated AI-model inference). Developers reach the platform through a web console, a REST API with Bearer/OIDC access tokens, an official Go SDK, a Terraform provider, a Kubernetes CSI driver, and the evroc CLI. The company emphasizes European sovereignty, sustainability, and security, operating from the Stockholm (se-sto) region.

human only

Limited machine-readable signal and partial portal coverage — documentation a human can read, but little a machine or agent can consume without scraping.

Kin Score

API Evangelist profiles evroc the way a machine reads it — 3 machine-readable artifacts, pulled from the provider's own public surface and indexed so a developer, an analyst, or an AI agent can evaluate it against every other provider on the network.

Every provider in the network is reduced to the same set of machine-readable artifacts — OpenAPI contracts, event specifications, GraphQL schemas, runnable collections, pricing and rate-limit signals, security posture, OAuth scopes, and the agent surfaces (MCP servers and skills) that let software drive the API on its own. We profile them because the interface is the part of a company you can actually inspect: it is a truer signal of what a provider does than any marketing page. From those artifacts we compute the Kin Score — evroc scores 35.6/100 (thin), with a separate agent-readiness read of 10/100 (human only). The full breakdown is below, followed by every artifact we hold — each card links through to its machine-readable definition on apis.io.

Kin Score

This is the API Evangelist rating — a single, repeatable read computed from the artifacts on this page. Green fill is points earned; the red track is points possible, so every bar shows earned-versus-possible at a glance.

Kin Score Kin Score How this is scored →
scored 2026-07-27 · rubric v0.5
Composite quality — 35.6/100 · thin
Contract Quality 0.0 / 25
Developer Ergonomics 13.0 / 20
Commercial Clarity 10.0 / 20
Operational Transparency 5.8 / 13
Governance 0.0 / 12
Discoverability 6.8 / 10
Agent readiness — 10/100 · human only
Machine-Readable Contract 0 / 18
Agentic Access Contract 0 / 15
MCP Server 0 / 12
Machine-Readable Auth 10 / 10
Idempotency 0 / 9
Stable Error Semantics 0 / 8
Request/Response Examples 0 / 7
Rate-Limit Signaling 0 / 7
Typed Event Surface 0 / 6
Agent Skills 0 / 5
Well-Known Catalog 0 / 4
Consent & Bot Identity 0 / 3

How we profile evroc

Each block below is one kind of artifact we hold for evroc. For each we say what it is and why it earns a place in the profile, then list every one we've indexed — capped at two rows, scroll within the panel for the rest.

Security Posture 3

Authentication, domain security, vulnerability disclosure, and trust-center signals — the evidence that a provider takes security seriously enough to document it. We profile it because you can't govern what you can't see.

Authentication, domain security, vulnerability disclosure, and trust-center signals.

Evroc Authentication

oauth2/http · 3 schemes

SECURITY

Evroc Domain Security

TLSv1.3 · DNSSEC · DMARC

SECURITY

Evroc Trust Center

ISO 27001, GDPR

SECURITY

Resources

Every other property we hold for evroc — documentation, portals, status pages, policies, and corporate surface — grouped by the job it does, following the integrator's arc from getting started to running in production.

Documentation 2

Reference material describing how the API behaves

Design & Contract 3

Pagination, idempotency, versioning, errors, and events

Build 4

SDKs, sample code, and the tooling you integrate with

Commercial 2

Pricing, plans, and the legal terms of use

Company 2

The organization behind the API

← All providers · Data indexed from github.com/api-evangelist/evroc · machine-readable index on apis.io