Full Automation with privacy at the core.
CLI>_ makes open-source cloud services practical for humans and non-human actors. People can use the web UI; agents, scripts, and automation can use documented APIs and GitOps workflows. The platform is built for clear ownership, repeatable operations, and private on-premise cloud on EU-located servers.
Full Automation
We are automation-led and built for everyone: humans using forms, and non-human actors using clear interfaces. The same service model should be understandable, auditable, and repeatable no matter who initiates the order.
Principles
Privacy is key to trust: customer data, code, documents, and operational metadata must stay under clear customer control.
Open to humans and non-humans: the web UI is for people, while documented APIs and GitOps workflows are for agents, scripts, and automation.
Open-source and transparent: we build the platform around open-source software, visible components, and no hidden black boxes.
Full Automation: every repeatable operation should become an API, script, job, or GitOps workflow instead of a manual ritual.
Built for long-term operation, not only experiments: common open-source projects need a stable managed platform for daily business use.
Current and secure stack: in the AI era, tools like Mythos can reveal critical bugs overnight, so our policy is to update quickly and keep the stack current.
We listen to feedback and keep improving the service, products, documentation, and operations.
UI and API together: different users need different interfaces, but the underlying service model stays consistent.
GitOps and declarative configuration: desired state belongs in versioned configuration, not in undocumented manual changes.
Open-source products like Gitea, Nextcloud, and Kubernetes runtimes instead of black-box hosting.
Transparent ordering: configuration, price, and resources must be explicit before confirmation.
Cookies and internal performance measurement
We use required cookies for secure operation and optional first-party performance measurement only after consent. We do not sell cookie data or use it for external advertising profiles.
Privacy-first data processing
Our Privacy Policy explains how account, billing, support, security, operational, and customer service data is processed for CLI>_ services.
Terms of Service
Our General Terms of Service describe the service model, acceptable use, billing, privacy-first operation, managed and unmanaged responsibilities, and legal baseline for using CLI>_.
Subprocessors
We list selected subprocessors used for infrastructure, billing, support, security, and operational services.
Security, abuse, support, privacy, and legal contacts
Use the dedicated aliases below so reports and legal/privacy requests reach the right operational queue.