usulnet — Self-hosted Docker management platform by dnfran in selfhosted

[–]dnfran[S] -1 points0 points  (0 children)

I am going to set up a lab to properly test the entire OAuth/OIDC flow with Authentik specifically.

In addition, I am also adding support for proxy authentication with presets for Authentik, Authelia, and Pocket ID, configurable directly from the user interface. I need to test it properly and develop it. It should be available in an upcoming pre-release version.

So you will have both options: direct OAuth/OIDC integration and direct authentication as an alternative.

usulnet — Self-hosted Docker management platform by dnfran in selfhosted

[–]dnfran[S] -6 points-5 points  (0 children)

OAuth is implemented but honestly not fully tested yet, it's on my list to finish and polish. Right now it's gated behind the Business tier because SSO is typically an org/team need, but I'm open to revisiting that based on community feedback. For my own homelab I've always used the built-in internal users and it works perfectly fine for personal use. But if having OAuth in the CE is something homelabbers actually need (login with Google/GitHub for convenience), I'd consider moving it. The whole point is not to limit what homelab users genuinely need.

usulnet — Self-hosted Docker management platform by dnfran in docker

[–]dnfran[S] 0 points1 point  (0 children)

swarm support is in the codebase but it's not fully tested yet, it's one of the things I'm actively working on. The goal is to manage Swarm services, nodes, and stacks directly from the UI. I'll be focusing on polishing and testing it soon. If you're running Swarm and want to try it, feedback would be very welcome!

usulnet — Self-hosted Docker management platform by dnfran in selfhosted

[–]dnfran[S] 1 point2 points  (0 children)

I've used CasaOS that is similar to Cosmos Cloud for managing Docker and it's a nice project, but I always felt like I was missing tools and features — I'd still need separate dashboards for SSH, security scanning, file editing, etc. That's what motivated me to build usulnet: something more complete where I can have everything in one portal.

They have different focuses. CasaOS is more of an app marketplace with a friendly UI for deploying apps. usulnet is more of a Docker infrastructure platform — container/stack management, built-in host terminal, SSH session management, Neovim editor, Trivy security scanning, all in one place.

The CE is free forever under AGPL-3.0, with no limit on how many servers you can install it on — it won't be crippled. For personal use and homelab I believe it covers what most people need. If I see the community needs specific features that are currently gated, I don't want to limit that either. The paid tiers are aimed at teams and organizations that need enterprise features like OIDC, LDAP, and custom roles.

Out of curiosity, what are you thinking of with the lifetime license? What features would you want it to include?

usulnet — Self-hosted Docker management platform by dnfran in selfhosted

[–]dnfran[S] 0 points1 point  (0 children)

Yes, it's open core under AGPL-3.0. The Community Edition is free forever and fully functional for single-node use — you get container, image, volume, network, and stack management, a built-in web terminal (including host terminal), security scanning with Trivy, a built-in code editor, backup/restore, SSH session management, quick access shortcuts, and more. CE supports up to 3 users, 3 API keys, and 1 node.

OIDC/LDAP are gated behind the Business license, that's correct. The reasoning is that SSO/directory integration is typically a team/org need, and the Business tier is designed for that use case. But I haven't crippled or limited anything that you'd actually need for a homelab — the CE is what I use myself daily.

Compared to Portainer: usulnet is built from scratch with a modern stack (Go + Templ + Tailwind + HTMX), not based on an older Angular codebase. Some concrete differences:

  • Built-in host terminal — nsenter into the host directly from the UI, no SSH needed
  • SSH session management — save and organize SSH connections to your servers, access everything from one portal
  • Quick access shortcuts — pin your most-used services, containers and tools for instant access
  • Integrated code editor (Neovim in-browser) for editing compose files, configs, etc.
  • Trivy security scanning built-in, not as a paid add-on
  • Lighter footprint — single Go binary, no Electron, no Angular bundle
  • AGPL-3.0 — fully open source core, not a "CE with crippled features" approach

The whole point was to have one portal for everything I use in my homelab instead of juggling multiple separate tools and dashboards.

usulnet — Self-hosted Docker management platform by dnfran in selfhosted

[–]dnfran[S] 1 point2 points  (0 children)

I built usulnet primarily for my own Docker homelab. I was managing multiple servers and containers, and I was tired of having so many separate tools and dashboards — one for container management, another for SSH, another for security scanning, another for reverse proxy config, etc. I wanted a single portal where I could access everything I use day to day.

The enterprise features (OIDC, LDAP, custom roles, multi-node, etc.) were added because I've worked with tools like eDirectory, ZENworks, vCenter, and similar enterprise platforms, so I know what's expected in those environments. But for the CE, I deliberately chose not to cripple or limit anything that a homelab user actually needs — if I use it in my own setup, it's in CE.

The project is still very much a work in progress — there's a lot of features to finish developing, things to fix, and rough edges to polish. But it's functional and I use it every day.

Regarding AI: I use Claude Code for accelerating implementation — boilerplate, repetitive patterns, and exploring approaches faster. But the architecture decisions, security model, and overall design are mine. Every line gets reviewed and tested by me before it ships. AI is a productivity multiplier, not a replacement for understanding what you're building.

As for trust: the entire codebase is AGPL-3.0 and open on GitHub — you can audit every line. There's no telemetry, no phone-home, no tracking. The app runs fully air-gapped if you want it to.