# Epinio

Epinio is a self-hosted development app. Epinio deploys Kubernetes applications directly from source code in one step. It is open source and self-hosted, installable on Kubernetes (Helm).

Canonical page: https://ourlocalhost.com/app/4821/epinio

## Description

Epinio deploys Kubernetes applications directly from source code in one step.

## Platform availability

Available on 1 of 10 platforms: Helm.

## Health score

69/100 (Good), based on 4 of 5 factors.
- Maintained: 100 (last commit 18 days ago)
- Popular: 56 (621 GitHub stars)
- Easy to install: 25 (1 install platform, install notes)
- Security check: 65 (no serious findings, 8 minor, CI, tests, OpenSSF Scorecard 5.7/10)

## Links

- Official website: https://epinio.io
- GitHub: https://github.com/epinio/epinio
- Documentation: https://docs.epinio.io
- Kubernetes (Helm): https://artifacthub.io/packages/helm/epinio/epinio

## Common questions

### How should staging workload configuration be configured in Epinio 1.13?

Epinio 1.13 reads staging workload configuration from an in-cluster ConfigMap. It is no longer configured directly on the Epinio container via ENV variables or Viper CLI flags.

### How are Epinio applications deployed and managed?

Applications can be deployed and managed with a single command.

### Why do self-hosters deploy Epinio on a Kubernetes cluster?

Self-hosting Epinio on a Kubernetes cluster can give developers the same experience and processes they have on Heroku.

### Is Epinio opinionated in its design?

The project is described as an opinionated platform that runs on Kubernetes.

---
Source: Our Local Host (https://ourlocalhost.com/app/4821/epinio), the self-hosted and open-source app directory.
