Open-source tools for the people who keep servers running.

Stackfly builds self-hosted software for infrastructure operators. Agentless by design: understand what is happening, investigate safely, and automate deliberately.

Try Playplane Browse the code on GitHub

Playplane

Your Ansible, with a shared view of who ran what, where, and what happened.

Playplane runs real Ansible against your existing infrastructure. Your Git repository stays the source of truth; Playplane adds targeting, live execution and a history the whole team can read.

Get Playplane on GitHub Read the docs

Target preview See which hosts a run will touch before it starts.
Live execution Per-host events and output as they happen, with check, diff, limit and cancel.
Run history Every run kept with its author, targets and Git revision, plus an audit log.
Access by project Viewer, Operator and Admin roles, enforced on the server.
Encrypted credentials SSH keys, Git HTTPS and WinRM secrets, injected only at run time.

Run it locally with Docker Compose

git clone \
  https://github.com/stackflyhq/playplane
cd playplane
make local-up
make create-admin

Then open localhost:3000 and sign in.

Demo Ansible › Live Running

WHERE · TARGET PREVIEW webservers:dbservers 5 hosts targeted 4 available · 1 unavailable

Hosts TopologyMatrix

control-node ansible-runner ansible-playbook

web3 · ssh web-01 web-02 web-03 1 changed · 1 running

db2 · ssh db-01 db-02 1 unreachable

running ok changed failed unreachable skipped pending

RUN #184 Running

Configure web tier nginx : Deploy site configuration

11 ok 3 changed 0 failed 1 unreach. 2 skipped

Playbook: playbooks/site.yml
Inventory: inventory/production.yml
Flags: --diff
Started by: marcelinux

Console 5 Playbook Variables Events 48 Filter output All hosts Following

PLAY [Configure web tier] ***********************************TASK [Gathering Facts] **************************************ok: [web-01]ok: [web-02]ok: [db-01]fatal: [db-02]: UNREACHABLE! => ssh: connect to host db-02 port 22: Connection timed outTASK [nginx : Install packages] *****************************ok: [web-01]skipping: [db-01]TASK [nginx : Deploy site configuration] ********************changed: [web-01]ok: [web-02]running on web-03

playplane Running

RUN #184 playbooks/site.yml

Configure web tier nginx : Deploy site configuration

11 ok 3 changed 0 failed 1 unreach. 2 skipped

web-01 web-02 web-03 db-01 db-02

Playplane's Live view during a run: targeted hosts, per-host state, result counts and the Ansible console.

Therapon

Pre-alpha

Fleet health, diagnostics and infrastructure understanding for Linux environments.

Therapon is being designed to turn read-only observations into understandable fleet health, signals and evidence-backed diagnostics, agentless by default. The aim: help operators see what is happening, why a system needs attention, and where to investigate next.

Therapon is being rebuilt from scratch around this new direction. There is no usable release yet; follow the repository as the new specification and MVP take shape.

The loop Therapon is designed around

01 Observe Collect typed, read-only facts from Linux systems.
02 Detect Turn observations into health states and signals that need attention.
03 Diagnose Follow declared read-only checks to understand what is happening.
04 Explain Trace conclusions back to evidence and point to the next useful check.

Each explanation leads back to observation: what to look at next, and why.

Unknown is a valid state.

A Therapon product principle

Facts before conclusions

Observations, health and interpretation stay separate, so every conclusion remains traceable to the evidence behind it.

Freshness is part of the truth

Fresh, stale and unavailable are different states. Last-known health never pretends to be current.

Diagnostics, not remediation

Declared read-only checks help you understand a failure, without turning Therapon, or any assistant built on it, into a remote shell.

Read the vision Follow on GitHub

The same rules for everything we ship.

Agentless

We use the access you already have, SSH first. Nothing to install and keep patched on every host.

Self-hosted

You run it on your laptop or your own server. Your inventory and credentials stay with you.

Built in the open

Code, specifications and roadmaps are public on GitHub, including what isn't finished yet.