How Staxly works

See it

Connect one subscription, read-only. Apart from that read-only access, nothing in your cloud changes.

What you do

• Give Staxly read-only access to one subscription. No password or key for your cloud is stored.

What you get

• Your cloud grouped into the applications you actually run, by what makes each one work. Where only a name or tag points to an application, Staxly shows the part there as likely and asks you to confirm.
• What is wrong with each application, and how sure Staxly is that its parts belong together.
• What Staxly could not place, shown separately, never hidden.
• A few questions about your estate. Staxly remembers your answers, and you can undo them.

What Staxly never does

• Changes anything
• Reads your data or your secrets
• Installs anything in your cloud

Fix it, with your approval

Let Staxly fix things, one approval at a time.

What you do

• Give Staxly permission to make changes. You can remove it whenever you like, without asking us.

What you get

• A named person approves each fix.
• Staxly makes the change and checks it worked. It can undo it, unless the cloud does not allow that, and then Staxly tells you before you approve.
• Every change written to a tamper-evident record for your auditors that nobody can edit afterwards.
• A fix someone undoes by hand shows up again.

What Staxly never does

• Changes anything without a named approval
• Acts on its own

The full product

Connect the tools your teams already use. A person still approves every change.

What you do

• Connect every subscription, GitHub, ServiceNow and Jira. For ServiceNow and Jira, Staxly keeps the sign-in you give it, encrypted.

What you get

• Every subscription read and re-checked every day.
• For parts your Terraform manages in GitHub, some fixes arrive as pull requests for your engineers.
• Staxly learns from your tools too: who owns what, and which code builds which application.

What Staxly never does

• Changes anything without a named approval
• Provisions anything