VerText
Don’t text. VerText.
Send anything to anyone through a vertex, even if they have not signed up yet.
VerText turns your verified email or phone number into a personal vertex identity. Send secure messages, files, streams, workflows, and live interactions through links anyone can open and respond to.
No app required to receive. No account required to reply. Create your own vertices when you are ready.
Your identity becomes a vertex
Your email or phone number already identifies you. VerText turns it into a programmable vertex identity for communication, sharing, automation, and live interaction.
Send to anyone
The recipient receives a secure link to the vertex. They can open it, read it, respond, upload, or participate directly in the browser before creating an account.
More than a message
A VerText can carry state, files, secrets, forms, streams, payment requests, workflows, AI agent interactions, and collaborative sessions.
Recipient experience
Incoming VerText
The recipient gets a link, opens a vertex, and participates directly in the browser.
Type: Secure Vertex
Expires: 24 hours
“Here is the document. Reply inside the vertex.”
A message becomes a vertex. A vertex can become anything.
Texting sends a message. VerText opens a vertex.
That means the interaction can be audited, expired, revoked, protected, replied to, connected into polygons, or transformed into a workflow.
Conversation Vertext
No app. No download. No meeting link mess. Just a vertex.
Create a secure conversation URL and send it to anyone. They open it in a browser, reply instantly, and can escalate from text to live voice, video, screen share, or real-time data when needed.
https://nodevertex.com/acme/support-call
Browser-first communication
Recipients open a URL and communicate immediately. No Node Vertex app is required to receive or respond.
Text first, live when needed
Every Conversation Vertext supports messaging. When text is not enough, upgrade to WebRTC audio, video, screen sharing, or data channels.
Governed like a vertex
A Conversation Vertext is easy to share, but still governed by Vertex Firewall controls, expiration, participant limits, and identity policy.
WebRTC live escalation
When text is not enough, a Conversation Vertext can become live.
With WebRTC support, a vertex can broker the secure signaling needed for browser-native voice, video, screen sharing, and real-time data channels. The media path can remain peer-to-peer when possible, while Node Vertex handles signaling, authorization, policy, and lifecycle control.
Use cases
Conversation links for real work.
Sales conversations
Move from inquiry to live call without scheduling friction.
Support calls
Start with a message, escalate to screen share.
Field technician video
Let a technician show the issue from a browser.
Incident response bridge
Create an expiring secure bridge during an outage.
IoT or agent troubleshooting
Use WebRTC data channels for live device or agent sessions.
Private consultation
One-time conversation links with expiration and audit lifecycle.
Security and privacy
A Conversation Vertext is easy to share, but still governed like a vertex.
Policies can support public links, invite-only access, email verification, phone verification, passkey identity, tenant authentication, expiration, maximum participant count, one-time access, disable-on-close, prevent re-entry, moderation, and recording disabled by default.
No app. No download. No account required to receive. Just a vertex.
Developer/API
Create a conversation in one command.
nv create conversation support-call --live audio,video --expires 1h
nv create conversation incident-bridge --live audio,video,screen --max-participants 8Conversation Vertexts expose text messaging APIs and a SignalR WebRTC signaling hub. High-frequency signaling stays off the durable database path while messages and lifecycle events remain auditable.
Create your first Conversation Vertext