Tools / Fukugen
Fukugen
Get back the stack file that is actually running on your Docker Swarm — verified against live.
Edits made in Portainer or with docker service update never make it back to your stack files, so redeploying the saved YAML quietly undoes them. Fukugen reads your live Docker Swarm and rebuilds the docker stack deploy YAML that matches what is running now. Every reconstruction is parsed back and compared field by field with the live spec before you can download it, so YAML that would deploy cleanly and do the wrong thing never leaves the tool. Export every stack to S3 on a schedule, and give clients their own login to a zone where they can see logs, restart, change environment variables and swap images for just their services.
Planned price at launch. Per major version, per instance.
In the workshop. It ships when it's ready.
What it does.
The YAML that is actually running
Pick a stack and get the docker stack deploy file for its live state, including changes made in Portainer or by hand. Copy it, download it, commit it.
Verified against live, not just valid
Each reconstruction is parsed back and compared with the live spec: network aliases, port publishing mode, entrypoint vs command, environment, secrets, replicas. If anything doesn't survive the round trip, the download is refused.
Export every stack to S3
One button, or one API call from your scheduler, writes every stack to your S3-compatible bucket under a timestamp, with a manifest of what succeeded and what didn't. Works with a write-only key.
Zones for clients and teams
Group stacks into zones and give people their own login. In their zone they can view live logs, start and stop services, change environment variables, swap images and redeploy, and nothing else.
Live logs in the browser
Tail any service's logs as they happen, with pause and clear. No SSH and no docker CLI needed.
Runs next to your swarm
Fukugen runs on a manager node of your own swarm and reads the Docker API directly. Nothing leaves your infrastructure, and the licence is verified offline.
Questions
What problem does Fukugen solve?
Portainer and docker service update change running services without updating your stack file. Redeploy the saved file and every one of those changes is silently reverted. Fukugen gives you the file that matches what is running now.
Does it work with Docker Compose or plain Docker?
Not yet. Fukugen reads Docker Swarm services and stacks today. Support for Compose projects on a single Docker host is being considered.
Are secrets redacted in the exported YAML?
No. Environment values are exported verbatim, because a redacted export looks valid and fails on restore. Treat exports as sensitive: use a write-only S3 key, encrypt the bucket, and never commit an export to git.
Why verify the YAML? Isn't docker stack config enough?
docker stack config only checks the file is valid. The failures that matter are valid files that deploy cleanly and do the wrong thing, such as a dropped network alias or a port published the wrong way. Only comparing against live state catches those.
What does Fukugen need to run?
A Docker Swarm manager node to read from, and a Postgres database for zones, users and sessions. S3-compatible storage is optional, for exports.
How will Fukugen be licensed?
A one-off purchase per major version, per instance, perpetual, with a 14-day full-function trial. No per-user or per-node fees.
Does Fukugen send anything back to you?
No. It never phones home, and the licence is verified offline. The only outbound traffic is the S3 export, to the bucket you configure.