Open-source project designed in Belgium
→
Privileged Access Management
Sensitive access, under control.
PAM-olive centralises, governs and supervises privileged access to your infrastructure from an open, modern and fully controlled platform.
Open source
Self-hosted
Traceable sessions
No unnecessary noise: we clean up privileges, not your bathroom.
Encrypted vault
Protected secrets
Active session
Live traceability
pamolive.eu
Protected
Overview
Console PAM
CO
Privileged session
Active
$ ssh admin@production
Secure and recorded session
$
Open-source project designed in Belgium
→
Privileged Access Management
Sensitive access, under control.
PAM-olive centralises, governs and supervises privileged access to your infrastructure from an open, modern and fully controlled platform.
Open source
Self-hosted
Traceable sessions
No unnecessary noise: we clean up privileges, not your bathroom.
Encrypted vault
Protected secrets
Active session
Live traceability
pamolive.eu
Protected
Overview
Console PAM
CO
Privileged session
Active
$ ssh admin@production
Secure and recorded session
$
Architecture & intégrations
Built to integrate, not to get in the way.
PAM-olive relies on a modern, modular, self-hosted architecture. Every component has a clear responsibility, simplifying deployment, maintenance and future evolution.
Python 3.12
Django 5.2
PostgreSQL 17
Redis 7.4
Channels
Celery
Docker Compose
AGPLv3
Modular architecture
Operational services
Every service in its place.
User access
HTTPS browser
PAM
Core application
Django + ASGI
Daphne & Channels
Persistent data
PostgreSQL 17
Users, policies and audits
Temps réel & cache
Redis 7.4
Channels and task queues
Automation
Celery Worker & Beat
Scheduled jobs and processing
Containers run with limited privileges
Independent and observable services
Deployment
Start cleanly.
PAM-olive peut être installé sur un serveur Linux disposant de Docker. Le script d’initialisation génère les secrets, protège le fichier d’environnement et démarre les services.
$ git clone https://github.com/pamolive/PamOlive.git
$ cd PamOlive
$ sh scripts/bootstrap.sh
✓ Secrets generated and services started
$ docker compose exec web python manage.py createsuperuser
$
$ cp .env.example .env
$ chmod 600 .env
$ docker compose up --build -d
$ docker compose ps
✓ PostgreSQL, Redis, Web, Worker and Beat are operational
$
Le mode HTTP intégré est destiné aux tests locaux. Une exposition publique doit passer par HTTPS et un reverse proxy correctement configuré.
Modular Django
Accounts, RBAC, Vault, Targets, Policies, Approvals, Sessions, Audit and MFA are separated into independent applications.
Controlled secrets
Sensitive data is encrypted with a key separate from the database and supplied through the environment.
Asynchronous tasks
Celery and Redis handle approvals, notifications, secret rotations and scheduled processing.
Tests from day one
An isolated test container validates the project with Pytest and currently enforces at least 85% coverage.
Self-hosted by design
Your accounts, policies and logs remain inside your own infrastructure.
A clean installation without bloating your infrastructure.
Architecture & intégrations
Built to integrate, not to get in the way.
PAM-olive relies on a modern, modular, self-hosted architecture. Every component has a clear responsibility, simplifying deployment, maintenance and future evolution.
Python 3.12
Django 5.2
PostgreSQL 17
Redis 7.4
Channels
Celery
Docker Compose
AGPLv3
Modular architecture
Operational services
Every service in its place.
User access
HTTPS browser
PAM
Core application
Django + ASGI
Daphne & Channels
Persistent data
PostgreSQL 17
Users, policies and audits
Temps réel & cache
Redis 7.4
Channels and task queues
Automation
Celery Worker & Beat
Scheduled jobs and processing
Containers run with limited privileges
Independent and observable services
Deployment
Start cleanly.
PAM-olive peut être installé sur un serveur Linux disposant de Docker. Le script d’initialisation génère les secrets, protège le fichier d’environnement et démarre les services.
$ git clone https://github.com/pamolive/PamOlive.git
$ cd PamOlive
$ sh scripts/bootstrap.sh
✓ Secrets generated and services started
$ docker compose exec web python manage.py createsuperuser
$
$ cp .env.example .env
$ chmod 600 .env
$ docker compose up --build -d
$ docker compose ps
✓ PostgreSQL, Redis, Web, Worker and Beat are operational
$
Le mode HTTP intégré est destiné aux tests locaux. Une exposition publique doit passer par HTTPS et un reverse proxy correctement configuré.
Modular Django
Accounts, RBAC, Vault, Targets, Policies, Approvals, Sessions, Audit and MFA are separated into independent applications.
Controlled secrets
Sensitive data is encrypted with a key separate from the database and supplied through the environment.
Asynchronous tasks
Celery and Redis handle approvals, notifications, secret rotations and scheduled processing.
Tests from day one
An isolated test container validates the project with Pytest and currently enforces at least 85% coverage.
Self-hosted by design
Your accounts, policies and logs remain inside your own infrastructure.
A clean installation without bloating your infrastructure.