macOS
Homebrewverified · 100%
brew install epiniolocal Homebrew formula metadata
brew / rank 6158
Install epinio with Homebrew
CLI for Epinio, the Application Development Engine for Kubernetes. Version 1.14.1 via Homebrew; verified 2026-07-30.
install
Additional install commands
overview
Package summary
CLI for Epinio, the Application Development Engine for Kubernetes
Project links
Commands and aliases
- epinio
history
Project history and usage
Epinio is a Kubernetes application-development platform and CLI that turns application source into a running URL in one step. Its documentation positions it as a PaaS-style abstraction over Kubernetes for developers who do not want to work directly with Kubernetes internals.
Project history
The GitHub repository was created in November 2020. The project was originally associated with SUSE and later lists Krumware and SUSE in the docs and copyright notices. Current documentation describes Epinio as a Krumware project in collaboration with SUSE.
Epinio evolved as a developer-facing layer over Kubernetes: the CLI pushes applications, Cloud Native Buildpacks and Paketo buildpacks can build them, and operators retain control of the cluster, ingress, service templates, and platform setup.
Adoption history
Epinio's adoption is concentrated in the cloud-native and Rancher/SUSE ecosystem rather than general-purpose Unix tooling. The official docs link Rancher-related projects, community Slack, and GitHub discussions, while the README documents release binaries and Homebrew installation for the CLI.
How it is used
Typical usage starts with a Kubernetes cluster plus ingress and certificate management, then installing Epinio through Helm and using the epinio CLI to create namespaces and push applications. The project targets teams that want a Heroku-like developer experience on top of Kubernetes.
Why package nerds care
Epinio matters to package nerds as a compact CLI entry point into a larger Kubernetes platform. Packaging the CLI through Homebrew makes the developer-facing part easy to install even though the running system depends on cluster-side components.
Timeline
- 2020: The GitHub repository is created.
- 2020-2024: Project copyright is listed under SUSE.
- 2025-2026: Project copyright is listed under Krumware.
- 2026: Official docs publish version 1.14.0.
Related projects
- Rancher, Fleet, Elemental, and Rancher Desktop appear as related projects in the official docs navigation.
- Paketo and Cloud Native Buildpacks are used for application build workflows.
Sources
security posture
Risk level: orange
infrastructure mutation or orchestration signal.
Risk classifier
orange risk · medium confidence · infrastructure
Why
- infrastructure mutation or orchestration signal
Signals
- text:kubernetes
Install behavior
- No Homebrew bottle metadata was recorded.
Recommended review
Before unattended agent use, check whether the tool reads plaintext credentials, writes remote state, publishes artifacts, or shells out to plugins.
executables
Installed executables
| Command | Kind | Exposure | Note |
|---|---|---|---|
epinio | executable | indexed executable | Discovered from the local executable index. |
freshness
Version and freshness
These signals separate page generation age, package-manager activity, and upstream release comparison. Version lag is warned only when an evidence URL and comparable versions are present.
page generated2026-08-03
manager version1.14.1
manager updated2026-07-30
local dataunknown
upstreamnot available
latest detectednot detected
- okNo freshness warnings were generated.
install metadata
Package metadata
| Package key | brew:epinio |
|---|---|
| Version | 1.14.1 |
| Package manager | Homebrew |
| Homepage | https://epinio.io/ |
| Repository | https://github.com/epinio/epinio |
| Last updated | 2026-07-30T15:23:02Z |
| Pulse | updated |
| Bottle | not recorded |
| Service | none declared |
source trail
Generated from repository data
This page is generated by av-web from the private package SQLite artifact built by scripts/generate-pkg-sqlite.py.
Combined YAML source
View the package source record on GitHub.
Used sources
- Geiger risk classifier
- cross-ecosystem install command graph
- curated package history
- pkg.so package database
- pkgdb category and tag curation