Terms of Service

1. Acceptance

By accessing or using axonpush, you agree to be bound by these terms. If you do not agree, do not use the service.

2. Service Description

axonpush provides real-time event infrastructure for AI agent systems, including event publishing, subscribing, distributed tracing, and webhook delivery. Plans, invoices, renewals, and account changes are coordinated directly with axonpush.

axonpush is offered in two forms, and several terms below differ between them:

• Hosted. You send data to infrastructure we operate and access it through app.axonpush.xyz.
• BYOC ("bring your own cloud", formerly "self-hosted").You deploy axonpush into an AWS account you control, under a licence key we issue. Your event data stays in your account and is never transmitted to us. Sections 5 to 9 apply only to BYOC deployments.

3. Accounts and API keys

You are responsible for maintaining the security of your account credentials and API keys. You must not share API keys publicly or embed them in client-side code. You are responsible for all activity under your account.

4. Acceptable Use

You agree not to:

• Use the service for any unlawful purpose
• Attempt to gain unauthorised access to other accounts or systems
• Transmit malware, spam, or abusive content through events
• Exceed published rate limits or abuse the infrastructure
• Reverse-engineer or scrape the service

5. BYOC licence and activation

A BYOC deployment requires a licence key issued by axonpush. Approval is granted case by case; there is no self-serve path. The key is what authorises access to the release artefacts, so an unapproved or inactive key yields no images and nothing to deploy.

A licence key activates against the first AWS account that uses it and remains bound to that account. Activation from a different AWS account is refused rather than silently rebound; rebinding is a support action, and you should contact us if you are migrating accounts.

Licences carry an instance allowance, three by default unless otherwise agreed. This allowance is not enforced technically: deployments beyond it will succeed and are surfaced to us rather than blocked, so that a redeploy or a disaster-recovery region never fails because of a counter. Exceeding your agreed allowance is a matter for your agreement with us, not something the software prevents.

6. Entitlement and continuity

Your deployment obtains a signed entitlement from our control plane at control.axonpush.xyz and re-checks it hourly. Each entitlement is valid for fourteen days, so an outage on our side does not interrupt your deployment.

That fourteen-day validity is also a limit. If your deployment cannot reach our control plane at all — including because you block it at the network level — the current entitlement expires after fourteen days and event ingest stops. Reads are unaffected. You cannot disable the check-in and retain an active licence, because the check-in is how entitlements are renewed.

7. Lapse, grace, suspension and revocation

Where a licence has a paid-through date, your deployment moves through the following states on its own clock:

• Seven days before the paid-through date: a warning is shown in your dashboard. Ingest is unaffected.
• Up to five days after it: a grace period. Ingest is still unaffected.
• After the grace period: event ingest and other state-changing requests are refused with HTTP 402.

In every state, read requests are never blocked. Your dashboard, your history and your exports continue to work, and data already stored in your AWS account remains there and remains readable. Renewing restores ingest at the next check-in with nothing to restore.

Separately from payment status, axonpush can suspend a licence, which places the deployment in the refused-ingest state described above at its next hourly check-in, or revoke it, which additionally ends access to release artefacts and therefore to future upgrades. We will give you written notice before suspending or revoking, except where immediate action is required to address abuse, a security incident, or a legal obligation. Suspension and revocation do not delete your data, do not make already-stored data unreadable, and give us no access to your AWS account.

8. Telemetry from a BYOC deployment

A BYOC deployment transmits an hourly check-in to our control plane containing: the release version and git SHA it is running; its AWS region and the AWS account id the licence is bound to; whether the optional analytics plane is enabled; the number of events ingested this period and since the previous check-in; an approximate item count and table size read from DynamoDB's own table metadata; and a health status.

The check-in does not transmit event payloads, span attributes, trace content, prompts or model output; organisation, application, channel or environment names; user names or email addresses; or any API key, secret or credential. Your deployment renders the exact payload it is about to send at /license/telemetry-preview, so the list above can be checked against what actually leaves.

9. Support diagnostics

Where you ask us for support, we may queue a diagnostics request that your deployment collects and uploads. There is no inbound access path and no cross-account role: your instance builds the bundle and sends it, on its own schedule.

A bundle contains health information, the names of configuration values without their contents, and recent error-level log lines from your deployment's own log groups. Log lines are scrubbed for email addresses, licence keys, API tokens, AWS access key ids, authorization headers and credentialled URLs before upload. That scrubbing matches known credential formats: it will not remove an identifier that appears inside free-text error content or a stack trace, so review a bundle before requesting one if that matters to you. Every collection is recorded in your own audit log and shown in your dashboard.

10. Service Disclaimer

axonpush is provided "as is" without warranty of any kind. Features, APIs, and commercial terms may change with reasonable notice. We target high availability but do not guarantee specific uptime, retention, or performance SLAs except where stated in a separately executed written agreement.

11. Data Ownership

You retain ownership of all data you send through axonpush. We do not claim any rights over your event payloads, metadata, or application data. We may use aggregated, anonymised usage statistics to improve the service. In a BYOC deployment we do not hold your event data at all.

12. Termination

We may suspend or terminate your access if you violate these terms.

Hosted. You may delete your account at any time through the dashboard settings. Upon termination, your data will be deleted within 30 days.

BYOC. Your data is in your AWS account and we cannot delete it; deleting or retaining it is entirely your decision. Ending a licence stops event ingest as described in section 7 and ends access to future releases. The software already deployed continues to run in your account, and everything already stored remains readable.

13. Limitation of Liability

To the maximum extent permitted by law, axonpush shall not be liable for any indirect, incidental, or consequential damages arising from your use of the service.

14. Changes

We may update these terms from time to time. Continued use of the service after changes constitutes acceptance of the updated terms.

15. Contact

If you have questions about these terms, contact us at legal@axonpush.xyz.