What beta means here
Velixnet is at a stage suitable for closed testing, not for broad reliance. Features may be incomplete, user experience may change, and internal handling may be tightened as operational lessons are learned.
The service may work well in many cases, but it is not a finished production service. Testing status updated on 11 September 2026.
Velixnet is at a stage suitable for closed testing, not for broad reliance. Features may be incomplete, user experience may change, and internal handling may be tightened as operational lessons are learned.
Do not rely on the service for urgent alerts, emergency communications, medical, legal, financial, workplace compliance, or any situation where delayed, lost, or unavailable messages could create serious consequences.
VXN uses established encryption libraries and keeps private keys on user devices. Encryption does not remove all risks related to service operation, metadata, availability or implementation.
Accounts, sessions, queues, contact rules, and interface behavior may be reset, throttled, or revised if needed to improve the service or respond to abuse during testing.
Use Velixnet for exploratory, low-risk testing. Keep expectations practical, verify important contacts carefully, and avoid placing high-consequence trust in an early test environment.