Identity-aware access to SSH, databases, Kubernetes, message brokers and internal apps.
Open source, written in Rust, and run on your own infrastructure.
$ limen login # a browser opens on your identity provider
$ limen ls
NAME KIND ACCESS AS LABELS
orders-staging ● postgres limen_read, limen_write env=staging team=payments
web-staging-1 ● ssh ec2-user, ubuntu env=staging
$ limen ssh web-staging-1 # a recorded session, with a one-hour certificate
$ limen db connect orders-staging # psql through Limen, no password to copy
$ limen explain orders-prod # which rule stops me?
$ limen request orders-prod --for 30m --reason "INC-123"
Nothing inside your network opens a port: the worker connects out to the proxy, and only the worker holds target credentials.
SSH · PostgreSQL · MySQL · Redis and Valkey · Kubernetes · MongoDB · OpenSearch · Elasticsearch · RabbitMQ · Kafka · internal web apps · anything else over TCP
Works with your own servers and with the AWS managed services (RDS, Aurora, ElastiCache, EKS, MSK, Amazon MQ)
| Repository | What it is |
|---|---|
| limen | The control plane, proxy, worker and limen CLI, the web console, and the docs |
| setup-limen | A GitHub Action that installs the limen CLI and logs a CI job in as a bot with its own OIDC token, so no secret is stored. In development; not published yet |
| terraform-provider-limen | Manage resources, roles and bots from Terraform or OpenTofu, through the management API |
| homebrew-tap | brew install limen-dev/tap/limen |
Important
Limen is pre-release. There is no tagged release yet. Everything is tested end to end, but against local stand-ins: Dex in place of a real identity provider, databases and brokers in containers, a local S3. Nothing has been verified against real AWS, Okta or Datadog. Evaluate it; don't put it in front of production systems yet.
Limen is Latin for threshold: the line you cross to get in.
Found a security problem? Please report it privately.