Terms of Service

Last updated: 2026-09-10 00:00 UTC

These Terms of Service ("Terms") govern your access to and use of the Axial Solutions LLC ("Axial Solutions," "we," "us") account portal at axialsolutions.io and kyriosforge.io (the "Portal") and your license to use KyriosForge and related products ("Software"). By creating an account, initiating a trial, or purchasing a license, you agree to these Terms.

1. Accounts & Authentication

You authenticate via Google or Microsoft. We do not capture, handle, or store your password; authentication is managed directly by your chosen identity provider. We receive an authorization token and issue a secure session cookie to manage your browser session. You are responsible for maintaining the security of your Google or Microsoft account and for all activity that occurs under your session.

Enterprise: unified organizational access (coming soon). Enterprise customers will be able to enroll their own SASL-capable identity server so that one organizational profile can centrally manage Portal login and license activation across multiple offices or deployments, rather than each office authenticating independently via Google or Microsoft. This applies only to Portal (account/billing) access — the Software itself already provides its own domain authentication, SSO, and access control independent of this Portal account layer. This capability is not yet available; contact us if you’re an Enterprise customer interested in early access.

2. Licenses, Trials, & Entitlements

License grant. A purchase grants a license to run the Software under the tier and term purchased (node count, deployment count, and CPU topology limits, as applicable to that tier — see “License tiers” below). The Software is licensed, not sold; ownership remains with Axial Solutions LLC.

License tiers. A “node” is any host running the KyriosForge agent; there is no limit on the number of containers or workloads a licensed node may run — you license the control plane per managed host, not per workload. A “deployment” is a distinct KyriosForge hub instance; the number of deployments you may run concurrently is fixed per tier. Current tiers (see the Pricing page for current pricing and term lengths — 1, 3, or 5 years):

• Community — free. Commercial use permitted, with no revenue ceiling. 5 nodes, 2 CPU sockets per node, 1 deployment. No trial clock: it does not expire.
• Student — free, non-commercial, individual instructional use. 5 nodes, 1 CPU socket per node, 1 deployment.
• Academic/Organization — free, non-commercial, for schools and nonprofits. 5 nodes, no CPU-socket cap, 1 deployment.
• Home — non-commercial personal use. 8 nodes, contractually capped at 1 CPU socket per node (see “Contractual vs. technical limits” below), 1 deployment.
• Home Plus — non-commercial personal use. 15 nodes, capped at 2 CPU sockets per node, 1 deployment.
• Business — commercial use permitted up to $10,000,000 in annual revenue. 15 nodes included, fixed (no volume curve), capped at 2 CPU sockets per node, 1 deployment.
• Business Plus — commercial use permitted up to $50,000,000 in annual revenue. 15 nodes included, scaling to 30 on the volume curve, capped at 2 CPU sockets per node, 1 deployment.
• Enterprise — commercial use, no revenue ceiling. 32 nodes included, scaling with the plan purchased (self-serve up to 1,000 nodes; larger fleets by negotiated agreement), no CPU-socket cap, with multiple concurrent deployments available as purchased. Unified multi-office organizational accounts are coming soon (see “Enterprise: unified organizational access” above).

Initial access & activation. A fresh installation of the Software receives an initial three (3) days of full-function, untethered access (no vendor contact required). By the end of that window, activation is required via a trial key or a purchased license key.

Trial period & rollover. Standard trials run sixty (60) days and need no account — you paste the activation request and paste the key back. A trial is anchored to the hardware it was activated on: that machine gets one, and re-activating it within the window returns the same expiry rather than extending it. Once spent, that hardware needs a purchase. If you buy a license before your trial ends, the unused portion is credited toward your purchased term, once per machine. If you would rather not run on a clock at all, the Community tier is free and does not expire.

Expiration & grace period. Following the expiration of an active paid license, a seven (7) day grace period is provided, during which the Software continues at full function so you can renew or migrate your data. Trials do not carry a grace period — a trial that reaches its 60-day limit without activation moves directly to read-only (see below).

Coverage, renewals, and re-activation. Your license expires when your coverage period ends — not a full term from whenever you last activated. Renewing extends that date, and renewing early adds the new term to the time you already have rather than discarding it. Re-activating an existing deployment re-issues the same entitlement and does not extend it.

Rehosting. A license occupies one activation slot per deployment, and holds one live key at a time. To move a deployment to different hardware, deactivate it in the hub — which produces a signed receipt — and redeem that receipt in the Portal to release the slot for the new controller. A key handed back this way stops working on the installation that returned it. If a receipt can’t be produced — the hardware failed, say — open a support ticket and we’ll work through it with you. We can release a slot by hand in that situation, but it’s a judgement call rather than something you’re entitled to: nothing outside the software can show us the old install is really gone.

Beta license slots. While a beta program is running, joining it issues you a beta license slot for that program — one activation, for testing the software the program covers. It carries Enterprise capability limits and the same usage restrictions as an Enterprise license. Coverage runs sixty (60) days and is renewable at no charge for as long as that program stays open; renewing early adds to the time you already have. Closing the program ends renewal — a key already issued keeps working until its remaining coverage runs out, it is not revoked mid-term — after which the software degrades to read-only like any other expiry. A beta slot is separate from anything you have purchased and never alters, consumes, or replaces it; you can hold both, and one beta slot per program.

Beta programs. We run beta programs from time to time, for any product or product version we choose. Each program is announced with its own scope, and participation is free and voluntary. Enrolling requires a Portal account. Places in a program are limited and may run out; when they do, enrollment reopens only if a place is freed or we widen the program. You may hold one place per program, and you may be enrolled in several programs at once — a program covering a new version of something you already run is a separate program, not a replacement for your existing license.

While a program runs, and when it ends. Enrolling issues a beta license slot (above), renewable at no charge for as long as that program stays open. You may leave a program at any time; your place returns to the pool and any beta license you hold for it stops renewing. We may close a program at any time and for any reason. On closing: enrollment and renewal end, no new activations are issued, and a key already issued keeps working until its remaining coverage runs out rather than being revoked mid-term — after which the Software degrades to read-only in the ordinary way. Closing a beta program never affects a license you have purchased.

What beta software is. Software offered through a beta program is pre-release. It may change, may behave in ways a released version does not, and may be withdrawn. It is offered as-is for evaluation and testing, and we do not recommend depending on it for anything you cannot afford to have interrupted. Participation may include access to program-specific areas of the community forum, which lasts as long as your participation does. We may recognise substantial contributions with a discount; whether we offer one, and how much, is our decision and is announced with the program rather than fixed here — it is a thank-you, not something participation entitles you to.

Contractual vs. technical limits. Node count and concurrent-deployment limits are technically enforced: the hub will refuse to enroll an additional node, or activate an additional deployment, once your license’s limit is reached. The CPU-sockets-per-node figure is measured and enforced: a node exceeding it is restricted to read-only, as described below. The commercial-use and revenue-ceiling terms above are contractual terms you agree to by purchasing a given tier — those the software does not measure, and we rely on your good-faith compliance, the same as our Pricing page FAQ says about revenue-based eligibility. Operating outside your tier’s socket, commercial-use, or revenue terms is a breach of these Terms regardless of whether the software permits it technically, and may result in license termination under Section 8.

Usage requirements and restrictions based on hardware. You must operate the Software within your tier’s node and CPU-socket limits. If a node’s hardware exceeds what your tier licenses — for example, a node with more CPU sockets than your tier allows — we will not cut off your access to that node’s data. Consistent with how the Software already handles an expired license, a node outside your tier’s hardware limits is, at most, restricted to read-only access (view and export, no changes), with an on-screen notice explaining why and what to do — the same license-status notice the console already shows for an expired license — until it’s brought back within your tier’s limits or you upgrade to a tier that covers it; you will never be locked out entirely for a hardware-cap issue alone.

Offline operation. KyriosForge does not phone home for standard execution. License validation is verified locally against a signed entitlement issued to you at purchase/renewal.

Price protection / continuity guarantee. Where advertised on the Pricing page, these commitments apply as described there; that page governs their specific terms.

3. Acceptable Use

You may not:

• Use the Software or Portal to violate any applicable laws or regulations.
• Circumvent, reverse-engineer, or tamper with the local cryptographic entitlement checks or licensing mechanisms.
• Resell, sublicense, or distribute license entitlements beyond your purchased tier’s stated scope (node/deployment/socket limits) without our explicit written authorization.
• Interfere with or compromise the security, integrity, or availability of the Portal or related services, or attempt to gain unauthorized access to other customers’ accounts or our infrastructure.

4. Support and Community Forum

Support is provided through our ticket system, and alongside it through the community forum. Ticket access and forum posting are tied to having an active, paid license under the terms described on the Pricing page, or to membership of the beta program while it is running; paid tiers are answered ahead of free ones. Reading the forum is open to everyone. We do not commit to a response time, and nothing here creates a service-level agreement — where one is wanted, it is agreed separately in writing. We may moderate or remove forum content that violates these Terms or is unlawful, and may suspend forum or support access for abuse. Posting is also subject to our community guidelines, which set out how the forum is expected to be used and how we moderate it.

5. Payments & Merchant of Record

Payment processing, order management, and invoicing are handled by our payment processor, Polar (polar.sh). Your billing information is processed under Polar’s own terms and privacy policy. Axial Solutions does not receive or store your payment card details. Prices are as stated at checkout; applicable taxes are calculated by Polar based on your billing location.

6. Limitation of Liability

The Software and Portal are provided “as is” and “as available” without warranty of any kind, express or implied, including warranties of merchantability, fitness for a particular purpose, or non-infringement. To the maximum extent permitted by law, Axial Solutions LLC shall not be liable for any indirect, incidental, special, consequential, or punitive damages, or loss of profits, revenue, or data. In no event shall our total cumulative liability exceed the total amount paid by you to Axial Solutions LLC in the twelve (12) months preceding the event giving rise to the claim.

7. Dispute Resolution & Mandatory Mediation

These Terms are governed by and construed in accordance with the laws of the State of Washington, USA, without regard to conflict of law principles.

In the event of any dispute, controversy, or claim arising out of or relating to these Terms, the parties agree to first attempt in good faith to resolve the dispute informally. If informal resolution fails, the parties agree to submit the dispute to confidential, non-binding mediation conducted in King County, Washington (or remotely via mutual agreement) prior to initiating any formal legal or arbitral proceedings.

8. Account Termination & Data Purge

We may suspend or terminate your account for violation of these Terms. You may also stop using the Software and request account deletion at any time. Upon deletion, your direct user identifiers are masked, while essential transaction references are preserved for accounting and audit compliance (see the Privacy Policy for the full detail). Hashed hardware footprints collected to prevent trial/registration abuse are retained for a maximum of five (5) years before complete purging.

9. Changes to these Terms

We may update these Terms — to state our responsibilities to you more precisely, to meet new regulatory or compliance requirements, or to keep the experience consistent as the product develops. A change takes effect when it is posted here. Every revision carries a date and time stamp at the top of this page, so you can always tell which version you are reading and when it changed. We notify registered account holders when these Terms change; if you do not hold an account, check that timestamp. Continued use of the Portal or Software after a change takes effect constitutes acceptance.

10. Contact

Axial Solutions LLC
Kenmore, Washington, USA
admin@axialsolutions.io

These Terms may change without prior notice; every revision is date- and time-stamped above, and registered account holders are notified when they do. We update them to state our responsibilities more precisely, to meet regulatory and compliance requirements, and to keep the experience consistent as the product develops — not to rewrite the arrangement you bought into. The price-protection and continuity commitments described here and on the Pricing page are the ones we hold steady.