A programmable redirect with Node Vertex controls.
Route users, devices, agents, payments, files, and workflows through a secure vertex with TTL, audit, firewall rules, authentication, and instant revocation.
Stop hardcoding handoff URLs. Use a Handoff Vertex.
A Handoff Vertex turns a URL into a controlled routing point. Instead of hardcoding checkout links, onboarding URLs, download routes, customer portal links, or app-to-app handoffs, create a vertex that can route traffic securely and observably.
https://nodevertex.com/acme/invoices/INV-10045/pay
→
Stripe Checkout today
→
Customer portal tomorrow
The public vertex URL stays stable. The destination can change behind it.
Controlled routing
Redirect using 302, 303, or 307 with HTTPS-only validation, allowed hosts, TTL, max hits, and one-time use.
Security first
Block localhost, private networks, raw IP targets, protocol-relative URLs, JavaScript, data URLs, and malformed destinations.
Workflow native
Use a Handoff Vertex inside payment, onboarding, device enrollment, support, form, agent, and activation polygons.
CLI examples
nv create go/demo '{
"type": "redirect",
"statusCode": 302,
"target": "https://nrun.com/demo"
}'
nv create invoices/INV-10045/pay '{
"type": "redirect",
"statusCode": 302,
"target": "https://checkout.stripe.com/c/pay/cs_test_123",
"ttlSeconds": 1800,
"controls": {
"allowedTargetHosts": ["checkout.stripe.com"],
"maxHits": 3,
"audit": true
},
"metadata": {
"purpose": "invoice-payment",
"invoiceId": "INV-10045"
}
}'
How it fits into polygons
Invoice Vertex
↓
Payment Handoff Vertex
↓
Stripe Checkout
↓
Payment Confirmation Vertex
↓
Activation Polygon
A vertex can hold a value. A vertex can receive a signal. A vertex can trigger a workflow. A vertex can stream data. A vertex can hand off to another destination.
Every workflow starts with a vertex.
A Handoff Vertex is the simplest way to route a person, device, agent, payment, or workflow from one system to another with programmable control.