- Free allowance
- MIT client and server; bore.pub is one shared public instance
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- not stated
- Identity
- anonymousno card, no phone
- Binding limit
- noneno named constraint binds
- Evidence
- documented6 sources; a first-party page was read and the sentence quoted
- Freshness
- stale on 2026-12-04checked 2026-11-03 (live); stale on 2026-12-04
| Free tier | MIT client and server; bore.pub is one shared public instance unit none; metered on none |
|---|
| Price | none stated |
|---|
| Limits | - per-ip-shaping no per-user byte cap: the whole public instance carried 1.5 TB in one month and 2.8 TB in a later month (figures from the instance's maintainer), with a standing request to 'be reasonable with how much data you transfer' and to use it for short-lived port exposure source
no limit of any of the six kinds was published for bore.pub: it is one shared public instance with no commitment, and the software imposes none |
|---|
| Binding | none Nothing in the vocabulary binds: bore.pub publishes no quota and imposes no rate. The operator's numbers are the ceiling of the whole instance, 1.5 TB in one month (2023-01-02) and 2.8 TB in one month (2024-08-01), so a single client at 1 TiB/month would be 39 to 73 per cent of everything the public instance was observed to carry, and the operator's answer to that was a request to reduce. |
|---|
| Identity | anonymous the software needs no account |
|---|
| Egress | self-host: the operator's NIC. bore.pub: shared, with no commitment |
|---|
| Interface | cli bore local PORT --to bore.pub |
|---|
| Tooling | part of the text of Free tier, above |
|---|
| Composes with | bore local PORT --to bore.pub reaches the public instance with no host; a bore server the user runs is the last resort. |
|---|
| Reliability | one shared instance on a single DigitalOcean host, funded by sponsorship, with a standing abuse problem: the author has publicly considered shutting it down and has had phishing reports on bore.pub |
|---|
| Notes | The public instance is not capacity a plan can rest on and was not measured. The record carried no limits. The operator's two posts give the only numbers that exist, and they describe the aggregate instance rather than one user, which is the distinction a reader needs. Quantifies what 1 TiB would mean relative to the observed aggregate, which is the only capacity fact the public instance has. The funding model and the abuse history are what make it unsuitable for a daily workload. |
|---|
| Evidence note | documented self-hosted bore 0.6.0 server and client on this host carried a 4,194,304-byte object byte-identically, sha256 46386cf4dbccceb80f80148d46d37f1a30d72912089cfbe4b3e51d9d55a79747, at 1.88 MiB/s against a 53.47 MiB/s direct baseline, so the software is measured. |
|---|
| Parsed numbers | |
|---|