Operations
Communication
WordPress Plugins
WhatsApp for WordPress
WooCommerce ↔ Relayno Stock
SoonReservations for WordPress
SoonSocial
Facebook Auto-Posting
SoonInstagram Auto-Posting
SoonERP
Odoo Stock Management
SoonREST APIs
WhatsApp API
Stock API
SoonHMS API
SoonCompany
About
Careers
Contact
About
Relayno started as a WhatsApp gateway for one shop. It grew into the platform that shop wished existed.
We built the first version for a retailer who was running stock in a spreadsheet, invoices in a desktop program, and customer chat on a phone behind the counter. Nothing talked to anything else, and the person paying for all of it was retyping the same order three times a day.
So we put the modules on one database. A sale moves stock, raises an invoice and messages the customer, because it is the same record — not three integrations that break the week after you set them up.
That principle has not changed. Every module we add has to earn its place by making the ones already there more useful, or it does not ship.
Modules on one login
Shared database
Languages, RTL included
Uptime target
Four rules that decide what we build and what we refuse to build.
One record, not five copies
If two modules need the same fact, they read the same row. Sync is a failure mode, not a feature.
Boring where it counts
Billing, permissions and message delivery should be dull and predictable. Save the cleverness for the parts nobody has to trust.
Your data stays yours
Full export in JSON and CSV, any time, no support ticket. Leaving should be as easy as joining.
Say the price
Published pricing, no per-module invoices, no quote-only tiers hiding what the thing actually costs.
A small distributed team, shipping in the open.
Remote, few meetings
Written first. Decisions live in documents so nobody has to have been in the room.
Ship weekly
Small releases behind flags beat quarterly launches nobody can roll back.
Support is engineering
Everyone who writes code answers tickets. The feedback loop stays short that way.