Velo
Velo is a self-hosted, multi-tenant AI WhatsApp platform for operators serving multiple clients from one installation.
Velo is a multi-tenant AI WhatsApp agent platform. You install it once and use it to run WhatsApp agents on behalf of several clients at the same time. Each client you serve is an organization — a tenant — with its own data, its own WhatsApp number, its own credentials and its own agent. Row-Level Security keeps every organization's data isolated from every other one at the database level, not just in the interface.
Customer messages become dependable work before ambiguity reaches the team.
WhatsApp sales usually fail at the handoff between an informal message and the back office that must fulfill it. Customers use nicknames, omit pack sizes, change quantities, and send voice notes while the team is already juggling stock, prices, and open conversations. When ambiguity is treated as certainty, the cost appears later as the wrong shipment, a correction call, or a rep rebuilding the order by hand. When every uncertain line becomes another private judgment, the operation cannot improve from one conversation to the next.
- WhatsApp transport (provider-agnostic)
- Orders capability
- Business-type orchestration
Each client runs differently without becoming another isolated installation.
Serving several clients from one product creates a management problem before it creates a scale problem. Each client expects its own data, number, staff, rules, and operating model, while the platform owner still needs one place to understand what is happening. Separate installations multiply upgrades and blind spots; loose shared access creates a worse risk by making every routine action a question of whose data is on screen. The business only scales when client differences remain deliberate and the owner's view remains coherent.
- Auth + multi-tenancy + RLS
- Business-type orchestration
- Custom (advanced) business-type
Client operations stay connected without making every handoff custom work.
Order data becomes expensive when it reaches the edge of the product. A sales team copies rows into a spreadsheet, an integrator rebuilds the same handoff for every client, and an automation cannot tell whether a partial request should be retried or reconciled. The visible cost is implementation time; the deeper cost is that every new client adds another fragile exception the operator must remember. A product business loses leverage when routine movement between systems depends on bespoke work and private operational knowledge.
- Audit logs (incl. agent actions)
- Connect API
- MCP server
- WhatsApp transport (provider-agnostic)
You receive this. It ships behind a feature flag and sits on the Pro+ tier as configured, so it is revenue you can reserve for your own paying customers.
You receive this. It ships behind a feature flag and sits on the Pro+ tier as configured, so it is revenue you can reserve for your own paying customers.
You receive this. It ships behind a feature flag and sits on the all tier as configured, so it is revenue you can reserve for your own paying customers.
You receive this. It ships behind a feature flag and sits on the all tier as configured, so it is revenue you can reserve for your own paying customers.
You receive this. It ships behind a feature flag and sits on the Enterprise tier as configured, so it is revenue you can reserve for your own paying customers.
You receive this. It ships behind a feature flag and sits on the Pro+ tier as configured, so it is revenue you can reserve for your own paying customers.
You receive this. It ships behind a feature flag and sits on the Pro+ tier as configured, so it is revenue you can reserve for your own paying customers.
You receive this. It ships behind a feature flag and sits on the Pro+ tier as configured, so it is revenue you can reserve for your own paying customers.
You receive this. It ships behind a feature flag and sits on the Enterprise tier as configured, so it is revenue you can reserve for your own paying customers.
You receive this. It ships behind a feature flag and sits on the Enterprise (Hosted-only) tier as configured, so it is revenue you can reserve for your own paying customers.
You are the operator. Tenant onboarding is yours to control: you create the client's organization, assign its number and choose its business type. Clients do not create themselves.
You receive this. It ships behind a feature flag and sits on the Enterprise tier as configured, so it is revenue you can reserve for your own paying customers.
The platform underneath the product — counted in this product's own source, not claimed from a template. Where a row carries a list, open it to read the names behind the number.
Coinbase
dLocal
Flutterwave
Komoju
Mollie
NOWPayments
Opn
Paystack
ActiveCampaign
Customer.io
Segment
Pushover
Twilio (WhatsApp)
Canny
Amplitude
Custom Head Scripts
fal.ai
OpenAI (embeddings)
Crisp
Tawk.to
Monday.com
Axiom
hCaptcha
Freshsales
Pipedrive
Pabbly Connect
AWS S3
MuxHover a table to isolate what it touches; click one to read its relationships. The big nodes are what everything else hangs off. organizations is referenced by 60 tables because every single record in this product belongs to an organization, and that is what makes tenant isolation a property of the database rather than something the application has to remember on every query.
all 73 tables, as text
active_boosts · admin_notifications · agent_conversations · agent_jobs · agent_messages · analytics_daily · analytics_events · analytics_funnels · announcement_dismissals · announcements · api_key_logs · api_keys · assistant_actions · assistant_conversations · assistant_messages · assistant_usage · audit_logs · automation_log · automation_templates · availability · bookings · business_types · catalog_items · client_zones · credit_balances · credit_transactions · currencies · data_exports · data_imports · faq_categories · faq_items · feature_flags · inbound_webhook_events · inbound_webhooks · knowledge_chunks · knowledge_documents · languages · marketing_audience_members · marketing_audiences · notification_log · notification_rules · notifications · order_lines · orders · organization_limit_overrides · organizations · plans · platform_secrets · platform_settings · price_list_items · price_lists · product_purchases · products · provider_prices · push_devices · report_templates · roles · scheduled_tasks · seo_meta · sku_aliases · subscriptions · tenant_agents · theme_page_sections · theme_section_library · theme_sections · translations · user_sessions · users · webhook_logs · webhooks · whatsapp_connections · whatsapp_contacts · whatsapp_templates
The chassis, and anything particular to this product. 3 required, 2 optional.
Runs Next 16.2.10; the application ships with React 19.2.3.
Provides the database, authentication, storage, and tenant data layer.
Runs the 4 jobs declared in `vercel.json`; wire them manually on another host.
Supports Brevo, Mailgun, Resend, SendGrid, or SMTP.
The example environment includes optional UPSTASH, NEXT, and SENTRY variable families.
Already built — plug and play
Every provider integration in this list ships wired into the product. You bring your own keys, connect them in the admin, and go live — there is no integration code to write. Nothing is resold through us: the ongoing cost is whatever these providers charge you. Capabilities marked plan-gated elsewhere on this page unlock by plan, not by extra code.
What exactly do I receive after purchase?
The complete source repository behind the live demo — 155,322 lines across the application and its database, 73 tables defined by 111 migrations that the shipped scripts apply for you, plus the seed data, the demo accounts and the setup documentation. Not a subset and not a scaffold: the same code that runs the demo you just used.
Is the live demo the same product whose source I receive?
Yes. The Velo demo runs the delivered release (v1.0.0), and the build figures on this page are measured from that same source — not from a showcase build kept separately.
Can I test every account role before buying?
Yes — all 4 of them: Tenant teammate, Tenant owner, Sales representative, Platform owner. Each one is seeded in the live demo and reachable from the role board above, so you can inspect the product from the customer's side, the agent's side and the administrator's side before you decide.
Is this a complete product or a starter template?
Complete. 84 page modules and 312 HTTP operations, with authentication, roles, billing, an administration panel, background jobs and seeded demo data all wired and running. A template gives you the shape of an application; this is one you can deploy and start operating.
Can I rebrand and modify it?
Yes, without asking. The name, identity, copy, styling and code are yours to change. Rebranding and operating it as your own service is exactly what the licence is for.
What does the licence allow?
A perpetual, worldwide, non-exclusive, non-transferable licence to the product you bought and to every update released for it. The Standard licence covers one business — yours. If you deploy for clients, the Client licence covers up to five. You can modify it, rebrand it, deploy it and charge your own customers.
Can I resell the source code?
No. Reselling, redistributing, sublicensing or giving away the source itself is not permitted under either licence. You build and deliver products with it — the code stays with you.
What services and ongoing costs are required?
You bring your own accounts, so we never mark anything up and there is no ongoing cost to us beyond the purchase. Required: Node host, Supabase, Scheduled job runner. Optional: Email delivery, Optional environment configuration. The table above says exactly what stops working without each one; most have usable free tiers at low volume.
How difficult is deployment?
Two ways, and most buyers use the first. The installer in your saascode dashboard walks it: you create free accounts at Vercel and Supabase, connect them, and it provisions the database, applies 111 migrations, seeds the data, deploys and verifies the result — you watch the steps go green. Or take the source and do it yourself with the shipped scripts and docs, which is the same sequence run by hand.
What updates and support are included?
Updates to that product for as long as we maintain it — no renewal fee and no expiry date on your access. Support covers download problems, defects in the code as shipped, questions about what the product does and how it is structured, and licence questions. It does not cover debugging your own modifications, building features for you, or setting up your hosting and third-party accounts.
Why does a complete codebase cost $299?
Because it was built once and is distributed many times. SaaSCode builds each product and ships the same finished release through the catalog, so the price reflects repeatable distribution — not a reduced codebase, an unfinished template, or what the same work would cost commissioned.
Do I need to be a developer?
No, for the normal path. You create free accounts at Vercel and Supabase, connect them to the installer in your saascode dashboard, and it does the deployment for you — provision, migrate, seed, deploy, verify. What it asks of you is creating two accounts and copying a token, not writing code. If you would rather deploy it yourself, or host it somewhere else, the full source and the scripts are yours to do that with. Running the product day to day needs no technical skill at all: that happens through its own interface, which is what the demo shows.