01 INSTALL
Get the CLI
Install the CLI directly from Endport.
npm install -g https://endport.io/downloads/endport-cli-0.1.0.tgz THE LOCALHOST TOOLKIT
Localhost
ends here.
Give your local API a public HTTPS endpoint and a private place to see every request. One command in your project directory. No email account.
Your URL stays yours. Keep the CLI running to stay online.
❯ endport 3000 --name myapp
ENDPORT v0.1Localhttp://localhost:3000
Publichttps://myapp.endport.io
Logshttps://workspace.endport.io/
CodeR7K2M-4WQ9P
Tunnel active ✓
IN YOUR BROWSER ↗ private
01Open the logs URL
02Enter the terminal code
YOUR API, ANYWHERE
PUBLIC HTTPS✳YOUR OWN DOMAIN✳REQUEST INSPECTION✳ONE SIMPLE COMMAND
01 / THE WORKFLOW
From local to live
in one terminal.
Run Endport in your app directory. The CLI creates a project URL, keeps the tunnel open, and prints a private logs code.
02 EXPOSE
Connect your app
Pick a name or let Endport use your project directory. Leave the CLI running.
endport 3000 --name myapp03 INSPECT
Open your logs
Enter the one-time code printed in your terminal.
workspace.endport.io/Node.js 20.19+ required · App identity is saved per project · Private credentials stay on your machine
WORKSPACE / PACKLY / TRAFFIC
⌑packly CONNECTED
PUBLIC URLhttps://packly.endport.io↗
REQUESTS / 24H184through this endpoint
SERVER ERRORS25xx responses
AVG. TIME84msto local response
TRANSFERRED2.4MBlast 24 hours
Recent requestsLAST 100
METHODPATHSTATUSTIME
POST/api/login20092ms
GET/api/users20043ms
POST/payments500112ms
GET/api/products20061ms
GET/health20018ms
InspectorREQUEST DETAIL
GET200
/api/users- Received
- 14:32:06
- Duration
- 43ms
- Request
- 0.8 KB
- Response
- 2.1 KB
Metadata only.
Bodies stay private.
TRAFFIC ▥ ANALYTICS ◇ DOMAINSAMPLE DATA · PRIVATE WORKSPACE
02 / THE WORKSPACE
See the request.
Find the issue.
Traffic has a home separate from your app. Open the private workspace to follow requests as they arrive and understand what happened before you switch back to your editor.
▤Live request activityMethod, path, status, timing, and transfer size.
▥24-hour analyticsHourly volume, errors, and your most active routes.
⌘Code from your terminalAccess stays tied to the project that created the app.
BUILT FOR THE DEVELOPMENT LOOP
The little details
do the work.
Endport keeps the setup close to your project and gives you the signals you need while your API is in motion.
Read the quick startOne directory. One endpoint.
Run the CLI inside your app. The assigned URL stays bound to that project, even when a preferred name needs a short suffix.
HTTP, WebSockets, and SSE.
Test APIs, live updates, and webhook callbacks against the same public HTTPS address.
A code from your terminal.
Request metadata appears in a separate workspace. The one-time code stays in your project terminal.
Bring the hostname you use.
Verify a DNS record once, then route a custom subdomain to your local server.
03 / MAKE IT YOURS
Your domain.
Your endpoint.
Use a ready to go Endport URL, or connect a subdomain your team already knows. Add its DNS records in the dashboard, verify it, then use the command below.
❯
endport 3000 --domain api.packly.ioBEFORE YOU RUN IT
A few things
worth knowing.
Clear answers for a tool that sits between your local server and the internet.
Does my URL stay online after I close the CLI?
The app name stays yours, but the endpoint goes offline when the CLI or local server stops. Run the same command in the project directory to reconnect.
Do I need an account to see logs?
No email account is required. Run endport code in the project directory, then enter the one-time code at workspace.endport.io/.
What does Endport store?
The workspace stores request method, path, status, timing, and transfer size for seven days. Headers and query strings are never stored. Optional redacted JSON body previews are off by default.
Can I use my own domain?
Yes. Add a subdomain in the workspace, create the CNAME and verification TXT records it shows, and verify DNS before connecting with --domain.
READY WHEN YOU ARE
One port.
Anywhere.
From localhost to a public HTTPS endpoint in one command.
See the setup guide