You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Datum was founded to help 1k new clouds thrive in the age of AI. Unlike existing alternatives, Datum’s open network cloud is built specifically for modern service providers, can be shipped anywhere, and is backed by an AGPLv3 open source license.
13
+
We believe that AI is changing everything — not just how we work and create, but how
14
+
quickly new applications, agents, and even clouds are being built. Digital
15
+
leaders today must orchestrate a complex, fragmented web of clouds, specialty
16
+
providers, customers, and data.
14
17
15
-
With Datum, cloud and AI-native builders can use the tools they love (like Cursor or a Kubernetes native CLI) to access the internet superpowers that today’s tech giants leverage at scale: authoritative DNS, distributed proxies, global backbones, deterministic routing, cloud on-ramps, and private interconnection.
18
+
The Internet is built on data center [meet-me
19
+
rooms](https://en.wikipedia.org/wiki/Meet-me_room), where telco providers and
20
+
hyperscaler clouds talk to each other over real physical cables, called
21
+
cross-connects. A new connection takes days or weeks of humans moving things
22
+
around to set up.
16
23
17
-
## Our Purpose
24
+
We believe the next era of the Internet is already here, and it's growing
25
+
fast. In the [alt-cloud](https://github.com/datum-cloud/awesome-alt-clouds)
26
+
universe, you don't think about virtual machines and VPCs, you think about
27
+
*services*. You connect your Vercel app with your Supabase instance all wired up
28
+
with your Kestra workflow, monitored by your Resolve SRE agent. There isn't a
29
+
switch or routing table in sight. It's just virtual plumbing to make your
30
+
business go.
18
31
19
-
We believe that most people devote their time, energy, families, reputations and money to something not because of what it does, but why it exists and what it believes about the world. When we introduce Datum to prospective users, customers, investors, partners or employees, here is what we share.
32
+
With Datum, cloud and AI-native builders can use the tools they love (like
33
+
Cursor or a Kubernetes native CLI) to access the internet superpowers that
34
+
today’s tech giants leverage at scale: authoritative DNS, distributed proxies,
35
+
global backbones, deterministic routing, cloud on-ramps, and private
36
+
interconnection.
20
37
21
-
- We are connectors — of people, businesses, apps and networks. ABCD!
22
-
- We are operators at heart who know how to get stuff done.
23
-
- We build for scale with thoughtful abstractions. "Our future selves will thank us."
24
-
- We believe that “open” is better, software is the customer, and partners have real value.
25
-
- We value grit, humility and hunger.
38
+
That's why we're building Datum: to help build 1k clouds in the age of AI.
26
39
27
-
## So What is Datum?
40
+
## So what is Datum?
28
41
29
-
### 🌍 Neutral by design
42
+
### Fully programmable and AI-native
43
+
44
+
- Developer- and agent-friendly protocols, interfaces, and workflows
45
+
- Programmatic interconnection between providers and services
46
+
- Security through network-level encryption that's built-in and impossible to break or disable
47
+
- Built using the "operating system for AI" Kubernetes API patterns for operator
48
+
tooling and familiarity (`kubectl`, Helm, etc.)
49
+
50
+
### Neutral by design
30
51
31
52
- No allegiance to a single cloud, vendor, or region
32
53
- Operates as a trusted, independent layer for alt clouds, incumbents, and
33
54
digital-first enterprises
34
55
35
-
### ⚙️ Fully programmable
36
-
37
-
- Designed for developers, operators, and modern service providers
38
-
- Built using Kubernetes API patterns for operator happiness and ecosystem
39
-
tooling (`kubectl`, Helm, etc.)
40
-
41
-
### 🛰 Bring your own infra
56
+
### Bring your own infra
42
57
43
58
- Use Datum’s cloud control plane along with its global network and distributed
44
59
compute
45
60
- Or run components in your own cloud or infra (e.g., GCP, AWS, NetActuate,
46
61
Vultr, etc.)
47
62
48
-
### 🔍 Observability & determinism
63
+
### Maximum flexibility
49
64
50
65
- Feed full telemetry to your preferred tools (Grafana Cloud, Honeycomb,
51
66
Datadog, etc.)
52
67
- Support for policy enforcement via SRv6
53
68
54
69
---
55
70
56
-
## 🚀 Some of our Favorite Features
71
+
## Some of our favorite features
57
72
58
73
### Declarative management
59
74
60
-
Define your desired infrastructure state using Kubernetes manifests. Datum
61
-
controllers continuously work to reconcile the actual state with your declared
62
-
configuration. This enables infrastructure-as-code practices and GitOps
63
-
workflows.
64
-
65
-
### Kubernetes native
75
+
Datum works just like Kubernetes, because it *is* Kubernetes. Define your desired infrastructure state and our components reconcile the living system to match. No more syncing or drift.
66
76
67
77
The Datum control plane is natively compatible with tooling from the Kubernetes
68
78
ecosystem. Datum APIs are defined as [Custom Resources][k8s-custom-resources],
69
79
and resources are managed by operators which can be deployed into any Kubernetes
70
80
cluster.
71
81
72
82
Use the tools you're familiar with - `kubectl` for interacting with API
73
-
resources via the CLI, `kustomize` or `terraform` for configuration management
74
-
via GitOps practices, or any other tool compatible with the Kubernetes API.
75
-
76
-
Expect the same behaviors from the Datum control plane as you would from
77
-
Kubernetes. Resources are reconciled to ensure intended state has been met,
78
-
failures are automatically addressed, and transparent status information is made
79
-
available.
83
+
resources via the CLI, `kustomize` or `terraform` for configuration management,
84
+
or any other tool compatible with the Kubernetes API.
@@ -95,17 +100,15 @@ Leveraging the standard Kubernetes Gateway API (`GatewayClass`,
95
100
`Gateway`,`HTTPRoute`, etc.), Datum allows you to define how external or
96
101
internal traffic should connect to your services. Manage TLS certificates,
97
102
configure routing logic, and control network ingress/egress across the
98
-
infrastructure managed by Datum.
103
+
Datum infrastructure.
99
104
100
105
## Components
101
106
102
107
### Datum API server
103
108
104
-
Built using Kubernetes API server libraries for compatibility with ecosystem
105
-
tools (`kubectl`, Helm, etc.), but focused on Datum-specific resources, not
106
-
standard Kubernetes workload types (like Pods or Deployments). This approach
107
-
takes advantage of recent developments in the Kubernetes project to build a
108
-
[generic control plane (KEP-4080)][kep-4080].
109
+
We deploy a Datum variant of the Kubernetes api-server in the style of the [generic control plane (KEP-4080)][kep-4080] so that we can leverage the vast ecosystem of libraries and tooling. There is no need to design a bespoke, infrastructure-focused distributed system for you to learn; Kubernetes has the primitives to support it. While the standard api-server operates normally for the cluster itself (think Pods and Deployments), Datum's api-server handles Datum-specific resources like `Network` and `Workload`.
0 commit comments