Terms of Service

1 · Agreement

These terms are between you — or the company you are acting for — and Topcmesh Labs, Inc., a Delaware corporation. Using the mesh at bus.topcmesh.com, holding a namespace, or using this site means you accept them. If you are agreeing on behalf of a company, you are confirming that you may bind it.

2 · What the service is

topcmesh is a realtime topic mesh. It accepts published messages and fans them out to subscribers holding open connections, in publish order, with replay from an acknowledged cursor inside a finite retention window.

It is explicitly not a durable queue, not a database, and not a system of record. Retention buffers are short and are overwritten on schedule. Do not use a topic as the only copy of anything you cannot lose.

3 · Cohort access

Access is granted in cohorts. A mesh key is issued to one team for one namespace, is non-transferable, and may be reissued or revoked when a cohort closes. Submitting a cohort request places you in a queue; a queue position is a record of interest and is not a contractual commitment by us to provide service, on any timeline or at all.

We may decline a request, and we do not always explain why. The usual reason is that the delivery contract does not fit what the applicant described.

4 · Acceptable use

• No unlawful content, and nothing that infringes another party's rights
• No malware distribution, command-and-control traffic, or unsolicited bulk messaging
• No attempt to reach a namespace you do not hold a token for, or to enumerate namespaces
• No load testing above your tier ceilings without telling us first
• No probing the mesh for vulnerabilities outside a written engagement with [email protected]

If you publish personal data of third parties through a topic, establishing a legal basis for that is your responsibility, not ours. We are a processor for payload content and act on your instructions.

5 · Limits and fair use

The published limits — 256 KB maximum payload, 2,000 publishes per second per topic, 10,000 per namespace, per-tier peak-subscriber ceilings and an 8 MB per-subscriber outbound buffer — are documented on the limits page and are enforced by the mesh, not by discretion.

Sustained operation above a tier ceiling starts a conversation about tiers. It does not trigger an immediate cutoff, except where the load threatens other namespaces, in which case we will rate-limit first and call you second.

6 · Retention and data loss

Retention windows are finite by design. A cursor older than its topic's window returns 409 cursor_expired. That is documented, intended behaviour and is not an outage, a defect, or an event that triggers a service credit. Your client must be able to resynchronize from your own source of truth.

7 · Availability

We commit to 99.95% monthly availability on the Mesh tier and 99.99% on Fabric, measured as successful publish acceptance and fan-out delivery to attached subscribers. The Signal tier carries no availability commitment.

Service credits are the sole and exclusive remedy for missing these targets:

• Below the committed level but at or above 99.5% — 10% of that month's fees
• Below 99.5% but at or above 99% — 25% of that month's fees
• Below 99% — 50% of that month's fees

Claims must be made within 30 days of the affected month. Scheduled maintenance, announced at least 72 hours ahead on the status page, is excluded, as is downtime caused by your own configuration or by traffic exceeding your tier ceilings.

8 · Fees

Subscription fees are billed monthly in advance. Overage is billed in arrears at $4 per additional million published messages. We give 14 days' notice before a price change takes effect for an existing namespace. Fees are non-refundable, including for partial months, and are exclusive of tax.

9 · Your content

You own everything you publish. You grant us only the licence necessary to receive, briefly buffer, and transmit those payloads to your subscribers — nothing broader, and nothing that survives the retention window. We claim no right to use your content for any other purpose.

10 · Termination

Either party may terminate on 30 days' written notice. We may suspend a namespace immediately for a breach of section 4, or where continued operation threatens the mesh. On termination your namespace stops accepting publishes and open connections are closed; retention buffers expire on their normal schedule. There is no data export, because there is nothing durable to export.

11 · Warranty and liability

Beyond the availability commitment in section 7, the service is provided "as is" and we disclaim all other warranties to the extent the law allows, including fitness for a particular purpose.

Our total liability under these terms is capped at the fees you paid us in the twelve months preceding the claim. We are not liable for indirect, incidental, special or consequential damages, or for lost profits or lost data, even if we were told they were possible.

12 · Changes to these terms

We may update these terms. Material changes are emailed to namespace owners at least 30 days before they take effect. Continuing to use the mesh after that date is acceptance; if you would rather not, terminate under section 10 and we will refund the unused portion of any prepaid term.

13 · Governing law

These terms are governed by the laws of the State of Delaware, without regard to conflict-of-laws rules. Disputes go to the state and federal courts sitting in Delaware, and both parties consent to that jurisdiction.

14 · Contact

Topcmesh Labs, Inc.
2261 Market Street, San Francisco, CA 94114, United States
[email protected]