Secure programmable URLs

Secure URLs for apps, agents, and automation.

Node Vertex lets teams expose applications, exchange state, and coordinate agents through policy-protected URLs. No custom API, webhook receiver, ingress stack, or one-off tool server required.

A normal URL points somewhere. A vertex does more: state, policy, identity, lifecycle, audit, expiration, files, events, routing, and automation.

Expose an app Create an agent conversation Talk to enterprise sales

App Vertex

nv app expose http://localhost:3000 --name demo --auth passkey --analytics --service --startup

Expose a local, private, containerized, or internal app through a secure programmable URL.

Agent handoff

POST /acme/agents/research-output
{
  "status": "complete",
  "summary": "market scan ready"
}

GET /acme/agents/research-output

Give agents a durable, governed place to leave work and trigger the next step.

What Node Vertex does

One fabric for app exposure, agent handoffs, and enterprise control.

Node Vertex gives every app, agent, device, workflow, and human a secure programmable URL.

1. App Vertex

Secure app exposure

Expose local, private, containerized, or internal apps through secure Node Vertex URLs.

Turn localhost into globalhost. Share a working app, preview, dashboard, tool, or runtime without opening inbound ports. Run it as a background service, start it at login, and surface broken local pipelines fast.

Explore App Vertex →

2. Agent Conversation Vertex

Multi-agent coordination

Create shared conversation spaces where humans and AI agents collaborate with full visibility, approvals, and workflow continuity.

Two agents and a human. One vertex. No misunderstandings.

Explore Agent Conversation Vertex →

3. Vertex Firewall

Enterprise policy and audit

Every URL gets policy, identity, lifecycle, and audit: authentication, method rules, IP restrictions, rate limits, payload policies, TTL, and evidence.

Explore Vertex Firewall →

App Vertex

App Vertex starts where secure tunnels stop.

It does not just forward traffic; it adds policy, identity, analytics, lifecycle, state, workflows, and agent handoffs around the URL.

Local development previews
Customer demo environments
Internal tools and admin panels
AI agent runtimes
Containers, private services, and home labs
Incident response and temporary client portals

Governed exposure in one command

nv app expose http://localhost:3000 \
  --name demo \
  --auth passkey \
  --analytics

Authentication, firewall rules, analytics, expiration, and routing live in the same vertex fabric.

Research to review to build

POST /acme/agents/research-output
POST /acme/agents/review-status
GET  /acme/agents/approved-work
POST /acme/workflows/build-trigger

Each step is a policy-protected rendezvous point with TTL, files, analytics, and audit.

Agent communication

Agents do not always need another server.

Sometimes they need a governed rendezvous point: a place to post results, pick up instructions, exchange files, or notify the next actor.

Node Vertex complements MCP, A2A, and other protocols by providing durable, policy-protected HTTP handoff points for state, files, review checkpoints, status, and workflow triggers.

Enterprise trust layer

Governed exposure for teams that cannot treat URLs as anonymous holes.

Node Vertex is built for governed exposure. Apply identity, firewall rules, method policies, expiration, rate limits, and audit to the same URLs your apps, agents, and workflows already use.

Security and Trust

PasskeysBearer tokensSigned linksTenant policiesMethod controlsIP restrictionsRate limitsTTL / expirationPayload validationAudit eventsApp analyticsAuthorized discovery

Solutions

Start with a concrete pain. Grow into the vertex fabric.

Secure internal tools

Give teams secure access to dashboards, admin panels, and operational tools without one-off ingress work.

Customer demo environments

Share live demos and preview apps with customers through expiring, authenticated, trackable URLs.

Webhook replacement

Use a vertex when you need a lightweight durable endpoint for payloads, callbacks, and events without building a receiver service.

Embedded Form Vertex

Talk with us through the same vertex fabric.

Use this secure Form Vertex to request App Vertex access, enterprise security details, or help designing an agent handoff.

The homepage does not post directly to an internal database. The embedded form is a vertex-owned intake surface that can emit structured events into Node Vertex workflows.

More Info Form Vertex

Secure intake for sales, security, and developer questions.

The product vision is simple: every workflow starts with a vertex.

Node Vertex gives apps, agents, devices, and workflows secure programmable URLs for exposure, state, handoffs, files, events, and automation.

Expose an app Developer docs