Platform nameservers
Fixed ayedo nameservers (ns1/ns2/ns3.ayedo.cloud) for delegation at an external registrar or in a parent zone ayedo does not manage.
Polycrate
ayedo Werkzeug- und Modellkette fuer Workspaces, Blocks, Specs und Releases.
48 of 214 items
Research and development at ayedo: Polycrate receives the BSFZ seal
The BSFZ recognizes the development of Polycrate as an R&D project. ayedo receives the red BSFZ seal for its in-house research and development work.
CLI Reference
Reference of all Polycrate CLI commands with options and parameters: workspace and block management, run, Git aliases, Kubernetes, observability, spec-driven development, operator, hub, and tools.
Polycrate Operator
The Polycrate Operator is a Kubernetes operator that synchronizes Ingresses, HTTPRoutes, nodes, backups, TLS certificates, volumes and deployed apps with the Polycrate API. Reference for CRDs, OperatorConfig, discovery controllers, S3Bucket provisioning, cloud controller and DNS webhooks.
Cloud Migration - Breaking Free from Hyperscaler Lock-in
Vendor lock-in at cloud hyperscalers, the portability obligations of the EU Data Act and a five-phase migration path with Polycrate to sovereign Kubernetes-native infrastructure, with examples such as AWS RDS to CloudNativePG.
Production Example: Software Delivery Platform
Example of a production-ready software delivery platform with Polycrate on bare metal: HA Kubernetes with floating IP, hardening, Cilium, Longhorn, VictoriaMetrics, VictoriaLogs and cert-manager as blocks in one workspace.
Troubleshooting
Guide to solving common problems with Polycrate: Docker, workspace, blocks, actions, workflows, SSH and performance, with problem descriptions and solution steps.
Updates
Updating the Polycrate CLI via the auto-updater with polycrate update or to a specific version from the Polycrate Hub.
Registry
Polycrate blocks are pushed to and pulled from OCI-compatible registries like Docker images, by default cargo.ayedo.cloud. Describes the architecture, authentication via Docker credential helper, configuration and exclude patterns on push.
Snapshot
On every action, Polycrate creates a snapshot of the workspace state for reproducibility, template injection and debugging. This page describes the mechanism, the contents and inspection with --snapshot.
PolyHub
hub.polycrate.io is the central platform of the Polycrate ecosystem: block marketplace and showroom, CLI download platform and update check server for polycrate update. Describes its features and its use as a DataSource in the Polycrate API.
Integrations
Overview of the Polycrate CLI integrations: configuration management and deployment, containers and orchestration, remote access, version control and AI integration, with an integration matrix, typical patterns and best practices.
Observability — Logs & Metrics from the CLI
Since CLI 0.46.0, platform logs and metrics can be queried directly from the terminal with polycrate logs and polycrate metrics. The CLI uses the Polycrate API as a proxy to VictoriaLogs and VictoriaMetrics.
Kubernetes
Native Kubernetes integration of the Polycrate CLI: kubeconfig search paths and inheritance, the debug pod via polycrate k8s debug, and kubeconfig synchronization from the Polycrate API with polycrate k8s sync-kubeconfigs.
API Integration
Polycrate's HTTP API integration with the PolyHub: configuration, ActionRun and CLI activity submission, template block publishing, maintenance window pre-flight, kubeconfig and encryption key management, the endpoint monitoring agent and CLI instance tracking.
Ansible
Polycrate's Ansible integration: snapshot variables in playbooks and templates, the workspace inventory, Ansible output configuration and the ansible-polycrate callback, Docker and Kubernetes examples, advanced playbooks and best practices.
K8s Addons
K8s Addons are catalog entries that let Kubernetes clusters subscribe to desired blocks and install them via the block rollout. Describes the layers, usage in the cluster detail view, version pins and enforcement.
Workspace Encryption
Built-in age-based encryption for sensitive Polycrate workspace data: key resolution, generating keys without the Polycrate API, encrypt/decrypt/status commands, API key management, team workflow, pre-commit hook, secret access in actions, .gitignore handling and troubleshooting.
SSH
Polycrate's native SSH integration: connecting to inventory hosts, interactive host selection, ssh exec, tunnel and copy, shell autocompletion, passphrase support, SSH agent socket mount, key source (sshkeysource) and Ansible become password.
Git Integration
Polycrate's native go-git based Git integration: status, add, commit, push, pull and sync commands, workspace aliases, auto-commit, SSH authentication, differences to external Git and troubleshooting.
Artifacts
Workspace artifacts in Polycrate: the artifacts/ directory structure, block artifact directories, the secrets directory, standard artifacts such as inventory and kubeconfig, using and generating artifacts in actions, and the migration from Artifact Discovery to template blocks.
Inheritance
Block inheritance in Polycrate: how block instances in workspace.poly inherit from template blocks via from:, config deep merge, overriding actions, inventory and kubeconfig conventions and best practices.
Dependencies
How Polycrate resolves block dependencies via from: in workspace.poly: interactive dependency prompt, --blocks-auto-pull, manual pulls, dependency sources, block versions as singletons and troubleshooting.
Naming Conventions
Validation rules for Polycrate identifiers: the lowercase slug for workspace, organization, action and workflow names, block names, and the extended metadata name with valid and invalid examples.
Best Practices
Short operating rules for Polycrate workspaces and blocks: workspace layout and naming, one environment per workspace, block versioning, metadata, actions and workflows, container, security and logging.
The Polycrate Container
The Polycrate container: concept and lifecycle, included tooling, mounts and environment variables, Dockerfile.poly for custom images, debugging with polycrate debug, container configuration, Docker native mode and troubleshooting.
Configuration
All configuration options in Polycrate: restrictions on template substitution, workspace.poly structure and keys, block instances, secrets.poly, YAML anchors, container configuration and the global CLI configuration in ~/.polycrate/polycrate.yml.
Why Polycrate?
Why Polycrate: simple actions instead of tool chaos, the toolchain inside a container, a single workspace.poly, team-friendly operations, reuse of existing code, Ansible integration, OCI registries for blocks and Git.
Workflows
Workflows orchestrate multiple block actions in a defined order: concept, workspace.poly definition, execution flow, prompts, allow_failure, practical examples, commands, best practices and troubleshooting.
Actions
Actions are the executable units of a Polycrate block: action schema, playbook vs. script, prompts, interactive mode, labels, action config, runtime overrides with --set and data persistence.
Blocks
Blocks are the modular building units of a Polycrate workspace: block.poly structure, block instances and template blocks, recommended metadata, vulnerability products, changelog and examples.poly.
Workspaces
A Polycrate workspace is a folder holding configuration, credentials and lifecycle artifacts. Directory layout, .state.poly, workspace init and clone, organization conventions and hybrid code + workspace repositories.
Installation
How to install the Polycrate CLI on Linux and macOS: via the Docker installer image or by downloading a release build from the Polycrate Hub.
New at ayedo: hands-on IT workshops for Cloud Native, Kubernetes and DevOps
Hands-on ayedo workshops on Kubernetes, Docker, GitOps, security and Polycrate: small groups, prepared cloud labs, online or on site.
Understanding Kubernetes, not just using it: ayedo now offers hands-on IT workshops
Technological independence starts with your own expertise. ayedo offers hands-on workshops on Kubernetes, Docker, GitOps and Polycrate for IT teams.
Polycrate Hub
Template blocks from the registry — live README, changelog and versions.
Spec-Driven Development
Spec-Driven Development with Polycrate: plan, implement, document and version changes. Canonical flow for workspace and block releases, exact gate table, agent integration.
Dev and Deploy
The canonical chain from spec to installed change: workspace release, block release without specs, push, pull all instances, install. Gates, non-gates and the MCP ops for every step.
Polycrate Development Operations Workshop
Hands-on Polycrate Workshop for development teams: CI/CD integration, software build & deployment, security and credential management. One day of intensive training. Made in Germany.
Polycrate Platform Architecture Workshop
2-day Polycrate Workshop for platform architects: Developing IaC blocks, Kubernetes integration, multi-cluster management and enterprise platforms. Made in Germany.
Polycrate Platform Operations Workshop
Hands-on Polycrate Workshop for platform operators: Actions, backups, monitoring, support workflows and app deployments. One day of intensive training. Made in Germany.
Polycrate Essentials Workshop
Hands-on Polycrate Workshop: Infrastructure-as-Code basics, GitOps workflows and collaborative DevOps teams. Learn Polycrate in one day. Made in Germany.
Polycrate Platform Building Workshop
Individual consulting and hands-on workshop: Infrastructure planning, software development lifecycle and building internal development capabilities. For MSPs and IT teams. Made in Germany.
S3 Storage
S3-compatible object storage on CEPH – operated by ayedo on EU infrastructure. For backups, application data, and static files with predictable costs from €0.05/GB/month.
Load Balancer
EU-wide Anycast TCP load balancing (Layer 4) – operated by ayedo on our own infrastructure. Own AS, BYOIP, and integrated endpoint monitoring. Made in Germany.