pdf accessCLOUD
Start a tunnel
PUBLIC BETAA shorter path to the internet.

Local ideas.
Public possibilities.

Give your local app a secure public address. Share a preview, receive a webhook, or connect an API — without opening a router port.

Create your first tunnel See how it works

Your machine. Your application. One outbound connection.

Architectural copper and frosted-glass portal sculpture
PDF ACCESS CLOUDFIG. 001
PRIVATE ORIGIN → PUBLIC POSSIBILITY
Outbound connectionsPublic HTTPS URLsA straightforward APIHTTP / HTTPS

01 / MADE TO CONNECT

Less infrastructure.
More of what you build.

A direct connection between the work on your machine and the people who need to see it.

01

Share work in progress

Turn a local application into a public preview. Keep your development workflow and send a URL.

02

Bring your API online

Receive HTTP requests and webhook callbacks on your local service through a stable tunnel address.

03

Preview a document

Share the PDF viewer or document app already running on your machine. The connector forwards the request.

02 / FROM LOCAL TO LIVE

Three steps.
One open connection.

  1. 01

    Create a tunnel

    Name your connection in the dashboard. Get a public address and a private connector token.

  2. 02

    Run the connector

    Download the connector and point it at your local port. Your application stays on your machine.

  3. 03

    Share your address

    Open the HTTPS URL to reach your app. Manage the connection and revoke access from your dashboard.

localhost:3000
PDF Access Cloud
HTTPSpublic URL
YOUR TERMINAL
# After setting your private connector token
$ node connect.mjs --port 3000

# Documentation: /docs/
● localhost:3000
  ↳ HTTPS
Node.js 22.13+ · macOS, Windows & Linux

03 / BUILT FOR YOUR WORKFLOW

Your tools.
A common language.

Create, list and remove tunnels with a small JSON API. Use your preferred language, script or automation.

Explore the API
cURLJavaScriptPythonGo
CREATE A TUNNELREST / JSON
curl -X POST \
  https://pdf-access-cloud.com/api/tunnels \
  -H "Authorization: Bearer $PAC_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"name":"my-first-tunnel"}'
POST/api/tunnels

Security

A considered foundation.

Clear controls for the connections you create.

Encrypted transport

HTTPS to the public endpoint and an encrypted outbound connector.

Separate credentials

Revocable API keys and a dedicated token for each connector.

Explicit access

Tunnel URLs are public. Use your app’s own authentication for private content.

Read the security notes

COMMON QUESTIONS

A little clarity.

What can I connect?

HTTP applications running on your computer: development sites, JSON APIs, webhook receivers and PDF viewers. The initial release supports HTTP request and response traffic.

Do I need to change my router?

No. The connector opens an outbound connection to the relay. You do not need to forward an inbound port on your router.

Is a tunnel private?

The connection is encrypted in transit, but the public URL is accessible to anyone who has it. Add authentication in your local application before exposing private data.

Does this replace Cloudflare?

This is an independent tunnel service focused on connecting local HTTP apps. It is not a global CDN, DDoS protection service or a replacement for Cloudflare’s full platform.

What are the beta limits?

Up to 5 tunnels and 10 API keys per account. HTTP request bodies are limited to 2 MiB and response bodies to 4 MiB and requests time out after 30 seconds. WebSocket apps and streaming responses are not supported in this release.

LOCAL → LIVE

Make your next idea
accessible.

Start with the application you already have.

Create your first tunnel