Datum
Datum is an open source network cloud built for AI, founded in 2024 and backed by $13.6M from Amplify Partners, CRV, Encoded Ventures, Cervin Ventures, Ex/Ante, Step Function, and Vine Ventures, and founded by Zac Smith and Jacob Smith (ex-Equinix, Packet). Datum gives AI-native developers and alternative cloud providers critical, neutral network infrastructure to compete at scale: an Envoy-based AI Edge with a Coraza OWASP WAF, Layer 7 HTTPProxy/HTTPRoute traffic management, authoritative DNS and programmatic domain management, QUIC-based secure tunnels (Connectors) powered by Iroh, and a Galactic VPC global backbone, all deployed across 17+ global network locations. The platform is exposed through a Kubernetes-style declarative control-plane API at api.datum.net, the datumctl CLI, an official MCP server, and packaged agent Skills, with OAuth 2.0 / OIDC authentication and a forever-free Builder tier. Core platform is licensed AGPLv3.
Datum publishes 1 API on the APIs.io network. Tagged areas include Company, Data, Cloud, Networking, and Edge.
Datum’s developer surface includes documentation, API reference, getting-started guide, engineering blog, support, pricing, signup flow, and 20 more developer resources.
Kin Score
APIs 1
Individual APIs this provider publishes, each with its own machine-readable definition.
Datum Cloud API
Kubernetes-style declarative control-plane API for managing Datum Cloud resources — projects, domains, DNS zones and record sets, gateways, HTTPProxies, HTTPRoutes, traffic prot...
MCP Servers 1
Model Context Protocol servers that expose these APIs to AI agents.
datum-mcp.yml
MCP SERVERSecurity Posture 2
Authentication, domain security, vulnerability disclosure, and trust-center signals.
Scopes 1
OAuth scopes governing access to this provider's APIs.
Resources
Get Started 3
Portal, sign-up, and the first successful call
Documentation 2
Reference material describing how the API behaves
Agent Surfaces 4
MCP servers, agent skills, and machine-readable catalogs
Design & Contract 4
Pagination, idempotency, versioning, errors, and events
Build 3
SDKs, sample code, and the tooling you integrate with
Access & Security 3
Authentication, authorization, and security posture
Operate 3
Status, limits, changes, and where to get help
Commercial 1
Pricing, plans, and the legal terms of use
Company 2
The organization behind the API
Other 2
Properties that don't map to a standard resource type