Skip to content
Broos IO Cloud

How your projects are protected.

Keys stored as hashes, encrypted secrets, roles that give only what is needed, a record of every change, and time to undo a mistake. Here is what Cloud does, in plain words.

Keys

API keys

What protects the keys your apps use.

  • Shown once, kept as a hash

    A key’s secret is shown when it is made and stored only as a hash.
  • Held to what it should do

    Restrict a key to some APIs, IP addresses or ranges, websites, an end date and a daily limit.
  • Rotation without downtime

    Rotating keeps the old secret working for the grace period you choose, up to seven days.
Secrets

Passwords and secrets

Where passwords live, and who may read them.

  • Encrypted

    Secret Manager encrypts each value with XChaCha20-Poly1305.
  • Never on a page

    Passwords for instances, databases, FTP logins and drives go straight into Secret Manager.
  • Reads are recorded

    Reading a value is a permission of its own, and every read is written down.
People

Access and sign-in

Who can do what, and how sessions end.

  • Roles

    From Owner to Secret reader, on an organization or one project, for good or until a date.
  • Activity log

    Who changed what, when and from where, for every project.
  • App sessions

    Sessions for Aria Workplace and Joi are stored only as a SHA-256, can be signed out everywhere, and end when a password changes.
Mistakes

Time to take it back

Deleting is rarely final at once.

  • Projects

    A project shut down is kept for 30 days.
  • Instances and drives

    Deleted ones are kept for seven days.
  • Keys and secrets

    Deleted ones can be brought back for 30 days.

Questions about security?

Tell us what you need to know.