TTryDataverseMessagingDeveloper docs ↗
TRANSPARENT PLATFORM READINESS

Where the platform stands.

We distinguish live public resources from independently tested private workflows and features still awaiting provider authorization.

Customer sending and payments are not publicly active. This page is an implementation snapshot published on 22 October 2026, not a real-time uptime monitor.

PUBLIC

Product website

Public information pages and developer integration reference can be accessed without an account.

Site publication
PRIVATE PREVIEW

Messaging dashboard

Accounts, contacts, templates, inbox, audit and delegated API workflows tested on a private staging server.

Not publicly accessible
NOT ACTIVATED

Commercial delivery

Real Meta onboarding, approved sender, outbound provider verification and Razorpay settlement are not complete.

Customer sending disabled
WHAT'S AVAILABLE

Current functionality snapshot

✓

Tenant isolation and API authorizationScoped application keys, PKCE delegated access and immediate authorization revocation tested with a real database.

✓

Light, mobile-first dashboardVisual and responsive testing performed on private desktop and mobile journeys.

✓

Consent-aware template/campaign preparationBackend validation and mocked Meta provider contract tested; live sending remains switched off.

–

Meta Embedded Signup and approved live deliveryRequires official customer/provider authorization and real end-to-end testing.

–

Billing, tax and merchant reconciliationRazorpay merchant capture and real category/destination tariffs must be verified.

–

Public production API and hardened hostingRequires a secure public backend deployment, webhooks, security validation and uptime monitoring.

Build on clarity, not promises.

We will only label provider-dependent workflows as operational after authentic acceptance and delivery testing, documented security checks and customer activation.

Explore developer contracts →Return home