💡 About Minaki APT

🚀 Why We Built This

Minaki APT was born out of necessity. We needed a secure, modern, and developer-first way to ship internal Debian packages — not just for ourselves, but for teams, startups, and builders that demand more than just a public PPA or an S3 bucket of `.deb` files.

Existing solutions felt clunky, locked down, or incomplete. We wanted more: authentication, auditing, CLI tooling, API access, and real-time control — without the enterprise pricing gatekeeping innovation.

🧠 Who It’s For

• Hardware & Firmware Companies shipping secure `.deb` updates to IoT, embedded, and robotics devices
• Internal Platform Teams distributing devtools across cloud environments
• Startups with bleeding-edge builds for private testers
• Open Source Projects that want curated, API-key gated access to privileged packages

🧩 What Makes Minaki APT Different?

• 🔐 API Key Auth Out of the Box: Powered by Kong + Keycloak. Every upload, pull, or delete is traceable.
• 🧾 Automatic Audit Trail: Deleted packages aren’t gone — they’re archived for compliance.
• 🧰 CLI-First Workflow: Upload, list, and remove packages with a slick terminal interface. Feels like Git — but for packages.
• 🛰️ Designed for CI/CD: Easy to integrate into your firmware or software deployment pipeline.
• 🛠️ Built to Be Extended: Open architecture. Webhooks, billing, analytics — all coming soon.

💥 Our Vision

Minaki APT aims to become the "Stripe for Secure Package Distribution" — fast, beautiful, API-first, and developer-obsessed. We believe DevOps deserves better than bloated enterprise tools or duct-taped shell scripts.

🙏 Thank You

If you're reading this — thank you. You’re part of a growing wave of builders who demand control, visibility, and trust in your build and release pipelines.

We’re just getting started. What we’ve built so far is the bicycle. But the supercar is coming. 🏎️