Skip to main content

Alpha status

Alpha status

Styrmin is currently in alpha. We're using it day-to-day and we want you to try it too, but you should know what that means before you commit to running it in anger:

  • APIs, CLI flags, GraphQL schema, and driver formats may still change between releases.
  • Breaking changes are possible without a deprecation window during the alpha phase. We try to call them out in the Changelog, but please read release notes before upgrading.
  • Styrmin is not yet recommended for production-critical workloads. It is suitable for lab, staging, and internal-tooling deployments where you can tolerate the occasional rough edge.
  • Expect rough edges in the UI, error messages, and documentation. We want to hear about them — see Giving feedback below.

Coming before beta

These features are deliberately not in the alpha and are tracked for the beta release:

  • Backup of a full environment — bundling every deployment in an environment into a single backup/restore operation. Tracked in opsmill/styrmin#7.
  • Cloning an environment — copy an environment (including selected applications) into a new, network-isolated environment. Tracked in opsmill/styrmin#6.

Known broken features

  • Infrahub Application backup is currently failing. The Neo4j pre-backup hook uses a Neo4j Enterprise-only command against the Community image bundled with the Infrahub driver, so the backup finishes in a PartiallyFailed state. Tracked in opsmill/styrmin#263.

If you hit something that looks broken and it's not listed above, please file an issue — see below.

Giving feedback

We're actively shaping Styrmin and feedback from early users carries a lot of weight right now.

  • Bugs and feature requests → open a ticket on GitHub Issues. If you're working inside the repository with an AI coding assistant, the create-issue skill (/create-issue) will format the issue to the project's conventions and apply the right labels — please use it for any bug report or feature request originating from your local workflow.
  • General discussion, questions, or "is this the right approach?" → join the OpsMill Discord. It's the fastest way to reach the team and the rest of the community.