Expose
expose.dev · 2 records in Egress and tunnels · JSON
Records 2
- caveatExpose (expose.dev managed service), Hobby
Egress and tunnelsidentity emailno cardevidence documentedstale on 2026-12-04disagrees
- paidExpose (expose.dev managed service), Pro
Egress and tunnelsidentity emailno cardevidence documentedstale on 2026-12-04disagrees
Expose (expose.dev managed service), Hobby
Egress and tunnelsSibling records disagree:
- verdict:
egress/expose-dev-hobbysays qualifies-with-caveat, egress/expose-dev-pro says paid-only
- Free allowance
- Free: TLS/SSL encryption, a time limit on every connection, random URLs, a single EU server; no card required
- Verdict
- caveatusable, with a named limit or an unprobed read path
- Cost
- not statedsee Price below
- Identity
- emailno card, no phone
- Binding limit
- noneno named constraint binds
- Evidence
- documented12 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 | Free: TLS/SSL encryption, a time limit on every connection, random URLs, a single EU server; no card required unit none; metered on wall-clock; The pages read name a time limit per connection but publish no duration and no byte figure. |
|---|---|
| Price | free; no per-byte price published |
| Limits |
The only published limit is a time limit with no number. |
| Binding | none Nothing countable is published: the free plan states a per-connection time limit without a duration and no byte cap, so no quota can be shown to fail first at 1 TiB per month. The tolerance is unpublished. |
| Identity | email a free account with full name, email address and password, or sign-in with GitHub or Google; an hCaptcha challenge is on the form; no card for the Hobby tier |
| Egress | no byte cap or transfer tolerance is published on the home page or the documentation pages read; the free plan has a per-connection time limit with no stated duration free allowance: none published |
| Per-object cap | not applicable: a stream |
| Retention | a random subdomain on every connect; the connection is time-limited |
| Interface | cli expose share http://localhost:3000; a web dashboard shows and replays the requests |
| Tooling | a PHP client (PHAR archive or Composer package, bundled in Laravel Herd) logs in to the managed server with an account token |
| Composes with | HTTP and HTTPS only on the pages read, so it fronts a web origin and is not a UDP forward or a WireGuard ingress. The open source PHP server can be run by the user on a rented or free machine as the last option. |
| Reliability | The free server is one data center in Germany; a connection is cut by the time limit and then gets a new random URL. |
| Notes | Managed lane of an MIT-licensed PHP tunnel (github.com/exposedev/expose). /pricing answers 404 and the plan table is on the home page. The byte cap is not published on any page read. |
| Evidence note | documented Home page, authentication page and registration page read on 2026-11-03; no limit figure is published, so the byte tolerance is unverified. |
Evidence 12
| date | source | what it proved |
|---|---|---|
| 2026-11-03 | expose.dev/ | the Hobby tier is free and needs no card |
| 2026-11-03 | expose.dev/docs/getting-started/authentication | the free plan is on one server in Germany, uses random tunnel names and has a time limit on every connection, with no duration stated |
| 2026-11-03 | expose.dev/docs/getting-started/authentication | sign-in is by email, GitHub or Google |
| 2026-11-03 | expose.dev/docs/client/sharing | the traffic shared is HTTP and HTTPS |
| 2026-11-03 | expose.dev/register | the registration form asks for full name, email address and password |
| 2026-11-03 | expose.dev/docs/getting-started/authentication | the free plan runs on one server in Germany, with random tunnel names and a per-connection time limit that the page gives no number for |
| 2026-11-03 | expose.dev/ | the Hobby plan needs a free account and no card |
| 2026-11-03 | expose.dev/docs/getting-started/authentication | sign-in is by email address, GitHub or Google |
| 2026-11-03 | github.com/exposedev/expose/blob/master/docs/client/sharing- | sharing a TCP port is marked as a Pro feature, so the free plan carries HTTP and HTTPS only |
| 2026-11-03 | expose.dev/docs/client/sharing | a user shares HTTP and HTTPS traffic |
| 2026-11-03 | expose.dev/docs/server/server/starting-the-server | the free server accepts client connections on port 443 |
| 2026-11-03 | faun.dev/toolbox/expose/ | the managed network is a separate proprietary service from the MIT-licensed PHP core that the self-hosted record covers |
More fields 4
| ingress | http-only |
|---|---|
| bytes transit | yes |
| transit note | the tunnel relays the bytes of the origin |
| volume stated | not published on the pages read |
Expose (expose.dev managed service), Pro
Egress and tunnelsSibling records disagree:
- verdict:
egress/expose-dev-hobbysays qualifies-with-caveat, egress/expose-dev-pro says paid-only
- Free allowance
- No free allowance on this tier; Pro is USD 79 per user per year, with no time limit
- Verdict
- paidno free allowance; listed for its price
- Cost
- no price statedsee Price below
- Identity
- emailno card, no phone
- Binding limit
- noneno named constraint binds
- Evidence
- documented4 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 | no free allowance on this tier; Pro is USD 79 per user per year, with no time limit unit none; metered on none |
|---|---|
| Price | USD 79 per user per year |
| Limits |
Nothing countable is published for the paid tier either. |
| Binding | none Nothing countable is published: Pro states no time limit and no byte cap, so no quota can be shown to fail first at 1 TiB per month. The tolerance is unpublished. |
| Identity | email an account with full name, email address and password, or sign-in with GitHub or Google; the plan cards say no card is needed to get started, and the checkout was not opened |
| Egress | no byte cap or transfer tolerance is published on the home page or the documentation pages read; Pro has no time limit free allowance: none |
| Per-object cap | not applicable: a stream |
| Retention | persistent URLs and reserved subdomains; no time limit |
| Interface | cli expose share http://localhost:3000; a web dashboard shows and replays the requests |
| Tooling | a PHP client (PHAR archive or Composer package, bundled in Laravel Herd) logs in to the managed server with an account token |
| Composes with | HTTP and HTTPS only on the pages read, so it fronts a web origin and is not a UDP forward or a WireGuard ingress. The open source PHP server can be run by the user on a rented or free machine as the last option. |
| Reliability | Pro uses the nearest server of a global network; the price is net of local taxes and VAT. |
| Notes | Team is USD 229 per team per year for up to 10 users. Paid-tier counterpart of the Hobby record; the home page publishes no byte cap for it. |
| Evidence note | documented Home page pricing cards read on 2026-11-03; the checkout was not opened, so the payment method is unverified. |
| Parsed numbers |
|
Evidence 4
| date | source | what it proved |
|---|---|---|
| 2026-11-03 | expose.dev/ | the Pro tier costs USD 79 per user per year |
| 2026-11-03 | expose.dev/ | Pro includes the global server network |
| 2026-11-03 | expose.dev/docs/getting-started/authentication | sign-in is by email, GitHub or Google |
| 2026-11-03 | expose.dev/docs/client/sharing | the traffic shared is HTTP and HTTPS |
More fields 4
| ingress | http-only |
|---|---|
| bytes transit | yes |
| transit note | the tunnel relays the bytes of the origin |
| volume stated | not published on the pages read |