Terms of service
Last updated 28 August 2026. Axela is operated by Roman Voronin, operating from Portugal ("we"). These terms are a contract between you and us. They are short on purpose, and nothing in them is hidden in the length they do not have.
Agreeing to them
You accept these terms when you register an organisation — the form and the API both say so at the moment you do it — or by using the service after we notify you of a change. You must be able to form a binding contract; if you are acting for a company or another person, you promise you are allowed to bind them, and "you" then means them too.
What the service does
Axela countersigns catalogs signed by a key you registered, stores them, and serves them to machines that ask. Before signing, it downloads the repository you published from, checks that the catalog describes those bytes, and examines the skills; it may refuse to sign a publication whose executable files do things we will not put our name to. Refusal is reported with the file and the reason.
That check is not a safety guarantee. A countersignature says who published bytes, that they have not changed, and that the check did not object — never that a skill is safe, correct or harmless. Deciding whether to trust a publisher remains yours.
The beta
The service is free while it is in beta, and comes with no uptime commitment. We may change or withdraw it; if we withdraw it, we will give at least 30 days' notice by email so you can move to a self-hosted notaryd, which is the same software under Apache-2.0. If we later charge for anything, that will be a new agreement you opt into, never a silent change to this one.
Your side
- Your account
- Keep your sign-in to yourself; what happens through your account is yours to answer for until you tell us it was compromised.
- Your keys and tokens
- Keep them safe. We hold only digests of your tokens and only the public half of your keys, so we cannot recover either — a lost token is rotated, a lost private key means a new one and a re-pin on every machine.
- What you publish
- It stays yours, and you are responsible for it. You grant us only the licence serving it requires: to store it and transmit it to machines that request it, for as long as you keep it published. Do not publish malware, anything unlawful, or anything you have no right to distribute.
- Fair use
- One organisation per account and reasonable volumes during the beta. Do not probe, overload or circumvent the service's limits or its authentication, and do not resell access to it. We may suspend an organisation that breaks these terms or that costs enough to threaten the service, and we will tell you why.
- Sanctions
- You may not use the service if applicable sanctions or export laws prohibit us from serving you.
Whose content is whose
The service's software is ours and its open-source parts are licensed under Apache-2.0 where their repositories say so; these terms give you no other rights to it. What you publish is yours. If someone shows us that published content infringes their rights or the law, we may remove it and will tell you we did; write to axela@system5.dev to report such content, and include enough detail for us to find and judge it.
Processing your machines' events
Events filed by your organisation's machines may contain personal data — machine names, hostnames, and through them the people who use them. For that data your organisation is the controller and we are your processor under GDPR article 28, and we commit to the following: we process it only to store it and show it back to your organisation; the people who could access it are bound to confidentiality; it is protected by the measures described in our privacy policy; we use the sub-processors named there and no others, and will notify you before adding one; we will help you, within reason, answer data-subject requests and security obligations that concern it; we will tell you without undue delay of a personal-data breach affecting it; and when your organisation is deleted, it is deleted with it, after which we retain nothing to prove otherwise. We do not touch it for any purpose of our own.
Our side
The service is provided as it is, without warranty of any kind, to the extent the law lets us say that. We are not liable for indirect or consequential loss, and our total liability is limited to what you have paid us in the year the claim arose — which during the beta is nothing. None of this limits liability that cannot be limited by law, including for death, personal injury, fraud, or our own wilful misconduct or gross negligence.
If a third party brings a claim against us because of content you published in breach of these terms, you will cover the loss that claim causes us. This is the mirror of the promise above, and it reaches no further than your breach.
Ending it
Close your account whenever you like, by writing to axela@system5.dev. We may close it for a breach of these terms, and will say which. Either way your catalogs stop being served, machines that pinned them keep verifying against what they already hold, and the privacy policy's deletion promise applies.
Changes to these terms
If we change these terms in a way that matters, we will email the address on your account at least 14 days before the change takes effect. Using the service after that is acceptance; if you do not accept, close your account before the date and nothing new ever applied to you.
The rest
If a court finds part of these terms unenforceable, the rest stands. These terms and the privacy policy are the whole agreement between us about the beta. A failure to enforce something once is not a waiver of it. You may not transfer this agreement to someone else without asking; we may transfer it to a successor who takes over the service on these same terms, with notice to you.
Law
These terms are governed by the law of Portugal, and its courts have jurisdiction. If you are a consumer, this does not remove protections or venues your own country's law gives you.