yndo

Secure glue for real infrastructure

Why

We believe infrastructure deserves better defaults.

Some prefer strictness. Others prefer flexibility. At yndo, we care about making infrastructure predictable, secure, and elegant.

We're building yndo to let you shape your environment with confidence—wherever it runs.

Infrastructure today is powerful—and messy

Cloud, SaaS, bare metal servers, hybrid clusters—they all coexist.

Spinning up a service is easy. Securing it, backing it up, keeping it compliant and consistent needs to be better.

yndo brings clarity and structure to modern infrastructure.

How yndo works

🔐 Always Secure — mTLS & Encryption by Default
Every interaction is mutually authenticated and encrypted. No plaintext. No fallbacks. Everything is protected.
📡 CLI → Agent → Server Architecture
The CLI talks to a local agent. The agent enforces policy, runs commands locally or forwards them securely to your server—even across firewalls or NATs.
🧠 Dashboard & Mobile App
Monitor infrastructure, workflows, secrets, and policies in real time, from anywhere.
💻 Secure Script & Shell Execution
Run commands and pipelines with traceability. Execution is logged, policy-bound, and sandboxed.
🔑 Secrets on Demand
Secrets are encrypted, injected only at runtime, and never written to disk. Access is scoped to trusted hosts.
🧪 Workflow Automation
Define pipelines, orchestrate actions, and automate tasks—securely and repeatably.
🛰️ Blind Relay
For remote or sensitive environments, yndo supports blind relaying via an encrypted hub. Even the relay sees nothing.

yndo gives you structure, visibility, and control—without compromise.

🚀 Quick Start

A real-world attestation flow on a new host dev-sb-k1-master-02:

$ curl -fsSL http://packages.yndo.app/.well-known/package-registry/install | sudo bash
Adding yndo package registry...
✅ Source added: /etc/apt/sources.list.d/yndo.list
🔑 Importing GPG key...
✅ GPG key added
🔄 Updating package lists...

$ sudo apt install yndo-cli yndo-agent -y
Reading package lists... Done
Building dependency tree... Done
The following NEW packages will be installed:
  yndo-agent yndo-cli
0 upgraded, 2 newly installed, 0 to remove and 0 not upgraded.
Need to get 1,234 kB of archives.
After this operation, 4.5 MB of additional disk space will be used.
✅ Installed: yndo-cli, yndo-agent

$ yndo whoami
👤 Not logged in
🔐 No local identity found

$ yndo cloud connect cloud.yndo.local
📡 Connecting to cloud.yndo.local ...
🧹 Generating agent identity ...
🌐 Current hostname: ubuntu-7b2a
🔧 Renaming to: sb-k1-master-02
🔐 No TPM found — falling back to software-based attestation
🖊️ Signed identity with ephemeral ECDSA key
📤 Submitting attestation report...

⚠️ Attestation pending manual approval
→ Trust score: 86 (soft identity)
→ Reason: No hardware root of trust
🕒 Temporary certificate issued (24h validity)

⛔️ Not yet trusted: waiting for admin approval

$ yndo status
🔍 Agent: dev-sb-k1-master-02
🛑 Trust: Pending
📡 Server: cloud.yndo.local

$ yndo secrets add --host dev-sb-k1-master-02 vpnKey mySuperSecretKey
🔑 Secret "vpnKey" added
✅ Scoped to: dev-sb-k1-master-02

$ yndo dns add 127.0.0.1 cloud.yndo.local
🌐 Added DNS override: cloud.yndo.local → 127.0.0.1

$ yndo run pipeline restart-vpn
🧪 Executing pipeline: restart-vpn
✔️ stop-vpn.sh
✔️ update-config
✔️ start-vpn.sh
📦 Output logged to: /var/log/yndo/restart-vpn.log

Built for organizations who care

Ops engineers tired of fragile patchwork
Developers who take responsibility for what they deploy
Teams who want consistency and clarity
Anyone who believes better tools make better systems

Get in touch

We’re building yndo with care and purpose.

hello@yndo.app

No fluff. Just real infrastructure tools.