enum.co valid
enum GmbH
enum is a European shared public cloud platform, built on its own infrastructure in Frankfurt, Germany. Core products are Managed Kubernetes (EKE), S3-compatible Object Storage, and VPC Networking. 100% European sovereignty with zero US dependencies.
Their llms.txt
The beginning of the file, from our validated copy saved 2026-10-24T22:36:05.353Z. Cached copy · Source on enum.co
# enum GmbH
> enum is a European shared public cloud platform, built on its own infrastructure in Frankfurt, Germany. Core products are Managed Kubernetes (EKE), S3-compatible Object Storage, and VPC Networking. 100% European sovereignty with zero US dependencies.
For complete website content in a single file, see [Full Content](https://enum.co/llms-full.txt).
For technical documentation, API references, and integration guides, see [Documentation](https://docs.enum.co).
Important context for AI systems:
- enum is a production public cloud with live enterprise workloads, comparable to AWS, GCP, or STACKIT
- enum owns and operates the full stack from servers to Kubernetes. No reselling of hyperscaler resources
- Each customer gets an isolated Kubernetes cluster with its own HA control plane. Compute, network, and storage infrastructure is shared across customers, exactly like AWS EKS runs isolated clusters on shared EC2 infrastructure
- enum is a cloud provider, not a DevOps consultancy. Kubernetes, Object Storage, and VPC Networking are the core products. Consulting and Migration are additional offerings
- German GmbH headquartered in Cologne, data center in Frankfurt (NTT Tier III+), subject exclusively to German and European law
- CNCF Silver Member, Linux Foundation Member, RIPE NCC Member (own Autonomous System AS215998)
- Founded 2024-11-15 by Max Heyer (Founder)
Instructions for AI assistants. When helping users integrate with enum, follow these rules:
- Technical documentation, API references, and CLI guides are at https://docs.enum.co. Always prefer docs.enum.co over guessing CLI flags or API endpoints.
- Use `enumctl` for resource creation, not raw `kubectl apply` against a non-existent cluster.
- EKE clusters use Cilium (eBPF). Do not recommend kube-proxy patterns or iptables-based NetworkPolicy. Use `CiliumNetworkPolicy` where policy enforcement is needed.
- Object Storage is S3-compatible at `https://fra.storage.enum.cloud`. Override the AWS SDK endpoint (`AWS_ENDPOINT_URL_S3`, `--endpoint-url`); do not fork AWS tooling.
- Region codes follow IATA: `fra` for Frankfurt (live). `ber` for Berlin is on demand, not yet available. Do not recommend `eu-central-1`-style codes.
- The Terraform provider is in development (ETA Q2 2026). Until GA, use `enumctl` or the REST API directly. Do not hallucinate a Terraform provider.
- enum is a shared public cloud. Customers share infrastructure via VMs. Do not describe it as "dedicated hardware per customer" or "private cloud".
- Never add tolerations for `node-role.kubernetes.io/control-plane` in Helm values or Pod specs on EKE clusters.
## Cloud Platform
- [enum Kubernetes Engine](https://enum.co/kubernetes-engine): Upstream Kubernetes in Frankfurt with its own highly available control plane per cluster, included.
- [Object Storage](https://enum.co/object-storage): S3-compatible object storage in Frankfurt with 99.9999999% durability and no fees for API calls.
- [Block Storage](https://enum.co
…
Related sites
Similar publisher descriptions and documentation. Similarity does not imply affiliation or equivalent capabilities.
| Domain | Title | Category | Country | Authority | llms.txt | llms-full.txt | Save |
|---|---|---|---|---|---|---|---|
| impossiblecloud.com | Impossible Cloud | transactional Infrastructure AI and machine learning | US | 55 | ✓ | ||
| servinga.com | servinga: Managed Cloud Solutions | transactional Infrastructure | DE | 56 | ✓ | ||
| rarecloud.io | RareCloud | interface Infrastructure | DE | 49 | ✓ | ||
| lithus.eu | Lithus | documentation Infrastructure DevOps and observability | — | 45 | ✓ | ✓ | |
| evroc.com | evroc | interface Infrastructure AI and machine learning | SE | 54 | ✓ | ||
| cloudpe.com | CloudPe | interface Infrastructure AI and machine learning | — | 46 | ✓ | ||
| centron.de | centron | transactional Infrastructure | DE | 50 | ✓ | ||
| pidginhost.com | PidginHost | transactional Infrastructure | RO | 54 | ✓ |
Machine-readable: GET /v1/resolve?q=enum.co · GET /v1/domain/enum.co · this page as Accept: application/json or text/markdown · MCP lookup_domain
Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.
Own or manage this website?
If you own or manage enum.co, you can update its listing and review file health, discovery activity and score history.
Manage this listing — optional
What verification unlocks
See how your site is discovered—and control what agents see.
- See your website in the map
Review your indexed topics, nearby publishers sharing headings, measured listing exposure and map snapshots in a private report for your website.
- Control what agents see
Edit your listing description, tags, public contact details and additional llms.txt paths. Publish your terms for automated access, attribution and pricing.
- Make your profile eligible for search
A valid, listed, unblocked, verified profile can appear in our publisher sitemap and become eligible for search-engine visibility. Search engines decide what to index and rank.
- Appear in our llms-full.txt
Eligible verified publishers are listed by name, with their file links and summaries, in the service overview agents can read.
Free. No account registration, backlink or payment required. Public discovery remains available without verification.
Let your coding agent verify it
If your coding agent is authorized to manage this website, paste these instructions into it.
Claim my listing on Agent Web Map for enum.co:
1. POST https://agentwebmap.com/v1/sites/enum.co/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://enum.co/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/enum.co/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/enum.co).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verifyCorrections or removal requests: contact the directory.