Standalone service workspace

LinkVeris

Shape what callers hear, where messages land, and what is live right now without digging through backend details or vendor control panels.

Tenant lsdaf-test-tenant
Portal portal.linkveris.dev
Call test Call path staged

Voice

SKYETEL

vpm

Database

do_db_cluster

provider_runtime

Assets

do_spaces

provider_runtime

Web access

dns published edge serving

portal.linkveris.dev

Live bundle

publication-646d7ba2a5baf343

runtime

Domain readiness

Domain readiness

A calm view of whether LinkVeris is only edge-ready, DNS-ready, or truly public-live.

Portal route

portal.linkveris.dev

Current state
dns published edge serving
TLS mode
public acme
Last verification
2026-03-16T04:37:21Z
Edge ready onlyDNS through VPM

Published hosts

Current standalone LinkVeris hostname set

Marketing
www.linkveris.dev
Portal
portal.linkveris.dev
Admin redirect
admin.linkveris.dev

What should I do next?

Beginner path

  • Use the portal host for operator access.
  • Treat edge-ready as internal validation, not public-live DNS.
  • Only call the domain live after VPM DNS reports ready, the route is verified again, and the TLS path is no longer internal-only.

Boundary reminder

Boundary reminder

LinkVeris reports readiness. VPM owns Cloudflare execution. Edge owns ingress and TLS termination.

Truthfulness rule

Do not overstate public-live status

If VPM DNS is still waiting for vendor config, the service may be edge-ready without being public-live. This page keeps that distinction visible.

Advanced domain detail

VPM DNS boundary

cloudflare through vpm

Runtime state
ready
Default zone
linkveris.dev
Vendor token present
Yes

Tenant rollout context

lsdaf-test-tenant

Organization
org-lsdaf-test-tenant
Live revision
rev-lsdaf-test-stage1-v2
Draft revision
rev-lsdaf-test-stage1-v3
Current bundle
publication-646d7ba2a5baf343