Every app
63 apps, and the 23 products that sell them.
The rest of this site is arranged the way you buy — by product. This page is arranged the way you look: if you came here for a point-of-sale, a rider app, or a helpdesk, it is on this list, with the product it belongs to beside it.
Every app
It opens on what needs you today.
Every app lands on a dashboard that shows the data it holds — not a wall of launcher tiles naming screens you already know are there.
Rutba Assistant · across the suite
Ask for the work, not the screen.
One assistant across the whole suite that acts as you — with your permissions, never beyond them — and shows its working by citing what it actually ran.
In every app
Tell us it is wrong, from the screen where it is wrong.
A control in the toolbar of every app that reports a bug, requests a feature or says something worked — and a strip on your dashboard that tells you what happened to it.
Rutba Suite
Run the business — sales, stock, orders, production, people, and the books, all sharing one customer list and one product catalog.
CRM
Contacts, leads on a board by stage, logged calls and meetings, follow-ups and saved segments — the system of record for who your customers are.
Helpdesk
Your own customer service desk: tickets and threads, routing rules you can test before they go live, and SLAs that count business hours — against the same customer record.
Customer Portal
A self-service window where your customers follow their orders stage by stage, message you about one, and ask to return the items they pick.
Marketplace
List on outside marketplaces or on another Rutba shop: catalog, price and stock pushed out, orders pulled in, and their status sent back.
Campaigns
Mailing lists, templates, audiences from CRM segments, one-off or recurring sends, and delivery reporting — email marketing end to end.
Social
Write a post once, schedule it to your connected accounts, and answer the replies in one place.
Affiliate Program
The back office for promoters: applications with due diligence, approval and suspension, agreements for each kind of promoter, and the program settings, with the application form on your own shop.
Storefront
Your online shop — product pages, cart, and checkout, driven by the shared catalog.
CMS
Pages, content, and landing pages for the storefront, without a separate website tool.
Point of Sale
The counter till — scan, sell, take payment by the shop’s own methods, and print, with stock deducted live; returns and exchanges priced by the server.
Stock
Products and the taxonomy that describes them, purchase orders, and the individual physical units that come off a delivery — the buying-and-cataloguing half of the group.
Warehouse Control
Warehouses and bins, per-location stock levels, the paperwork that moves stock between them, counts and reordering — the warehouse half of the group.
Procurement
Requisitions and approvals, sourcing and RFQs, supplier qualification, contracts and price lists, purchase orders, receipts and three-way matching, and a spend view.
Orders
The channel-neutral order hub — picking, packing, dispatch, invoicing, and returns.
Rider
The driver app: assigned runs, navigation, proof of delivery, and cash collected — offers, deliveries and availability kept when the signal drops.
Dispatch
The transport controller's board: consignments, parcels and stops, trips and manifests, carriers and rate cards, proof of delivery and cash reconciliation, and an exceptions queue.
Track
The delivery page your customer opens from a message - one consignment, no account, on a phone.
Manufacturing
Work orders and the job cards under them, bundles, the materials issued against them, and the people paid by the piece for them — with bills of material carrying versions, effectivity and the release that pins what the floor will build.
Planning
Demand and forecasts, the master schedule per branch, the time-phased MRP run, planned orders with pegging, firming, exceptions and the production timeline.
Shop Floor
The operator terminal on a shared device: clock on by PIN, take the dispatch list for the bench, start and stop an operation, report output and downtime — offline if it has to be, and an andon board the floor reads from across the room.
Quality
Inspection plans and the inspection queue, holds, non-conformances, corrective actions, supplier quality and certificates.
Maintenance
Machines on the asset register, meters, preventive schedules, and requests and orders with parts and labour.
Assets
The register of everything owned that is not stock: custody, lifecycle, contracts on things, licences, vehicles and audits.
Facilities
Sites and spaces, occupancy, leases, contractors and their documents, service contracts, and requests, orders and planned work.
Fleet
Vehicles and their operating profile, drivers and licences, walkaround checks and defects, duty and hours, fuel, incidents, cost per kilometre.
HR
The employee master and the org structure around it — records, contracts, departments, teams, matrix reporting, lifecycle events, letters and the asset register.
Employee Self-Service
One person’s own record: leave, attendance, schedule, payslips, expense claims, documents, assets, benefits, training and performance — plus somewhere to raise a grievance or report a safety incident, and a manager’s approval queue that appears only if the org chart says you manage anyone.
Payroll
Pay runs created, previewed, processed and paid — with deduction rules, salary structures, statutory remittances, and the accrual split by cost centre so a department can be asked what its people cost.
Time Clock
The shared wall device: badge or PIN, an offline queue for when the network is not there, and no biometrics and no location tracking by design.
Workforce
The operational week that line managers run rather than HR: the rota, absence, attendance, exceptions and timesheets against the hours the clock actually recorded, with an approval state machine payroll locks when it pays them.
Recruit
Requisitions, the candidate pipeline, interviews and offers — and the public careers pages candidates apply through: each job with its form, a status page for the candidate and a link to book the interview.
Talent
After the hire: reviews, goals, 360 feedback and check-ins, plus the course catalog, skills, development plans and succession.
Books
The daily surface: invoices, bills, receipts, supplier payments, credit notes, quotes, banking and reconciliation, expenses, collections and the customer and supplier ledgers.
Accounts
The accountant’s workbench: chart of accounts, journals, opening balances, tax and periods, tax returns, year end, budgets, projects and cost centres, currency, the general ledger and the financial reports.
Rutba Workspace
Run the day — email at your own domain, files, documents, chat, meetings, and phone, each logging back to the business record it concerns.
Webmail
The web client — inbox, search, folders, shared inboxes, meeting invitations shown as cards, and each message filed against the record it concerns.
Mail Gateway
The mailbox service: inbound delivery, storage, and IMAP access from any mail app.
Sign
Compose an envelope — documents, parties, signing order, fields, expiry — then track it and collect the sealed result.
Signing engine
The envelope, the append-only evidence ledger, and the seal over the completion manifest.
Verify
The public check: paste the reference from a document and see whether Rutba countersigned it, and when. No account, and free forever.
Docs & Sheets
The editors - documents and spreadsheets, edited together in real time, with a ribbon over both.
Workspace service
The document engine: format fidelity, co-editing sessions, and the live data bindings into your business records.
Chat
Channels, DMs, and record threads - one of the three surfaces in the Rutba Comms app, alongside Meet and Calls.
Meet
Calendar, scheduling, the session ledger and the meeting room itself - one of the three surfaces in the Rutba Comms app.
Calls
Numbers, click-to-call logging and the call ledger — one of the three surfaces in the Rutba Comms app, and the half that is running today.
Deskphone
The screen somebody taking calls lives in all day: the call ringing, who is calling and what Rutba already knows about them, answer, hold, transfer, and the wrap-up that turns a finished call into a disposition on the record.
Switchboard
The administrator’s side: DIDs and trunks, inbound routes, business hours, IVR menus, queues, extensions, and the recording and retention policy over all of it.
Voice campaigns
Outbound calling as a campaign rather than a phone system: audiences from the CRM, a dialling strategy, and per-call outcomes written back to the record.
Platform services
Power the rest — sending, storage, publishing, creative, and on-premise video. Every one sells on its own and underpins the suites above.
Send API
The HTTP send API - one call per message, with templates, tagging and the delivery record.
SMTP relay
The same transport for anything that already speaks SMTP, so an existing app can point at it and change nothing else.
Bounce & suppression
Bounce and complaint handling with a suppression list, so a bad address stops costing you reputation.
Media origin
The image and video origin: masters in, every size out on request, CDN-facing.
Upload provider
A drop-in upload provider so a CMS stores its assets here instead of on its own disk.
Relay console
Where posts are written, scheduled and watched - connections, calendars and the delivery record.
Publish API
The documented HTTP API and SDK the console itself is built on, so anything else can publish the same way.
Agent tools (MCP)
The same publishing surface exposed as Model Context Protocol tools, so an assistant can draft and schedule with the same permissions a person has.
Signing API
The authenticated surface — envelopes, templates and the sealed result at /api/sign/v1, with sgk_ bearer keys and signed webhooks. Runs inside your own instance, beside the documents it signs.
Public verification surface
Verification by digest — a sealed record's, or a single party's receipt, countersigned the moment they acted — the published key set and abuse reporting, served by the platform rather than by your instance; so a counterparty checks a document without a key, without an account, and without reaching your systems. Behind the same platform, the formality desk that arranges a stamp, seal or notarisation your sender asked Rutba for.
SDK
A dependency-free client, one method per endpoint, held to the API’s own OpenAPI document by a test.
Studio
The editors, brand libraries and deck designer - video, image and slides, rendered in the browser you are already in.
Render worker
The queue for the renders a tab cannot do: unattended runs, batches of one template across many products, and a guaranteed MP4.
Vision server
The recorder and its viewer, running on your own hardware. We license and support it; the disks and the footage never leave your building.
Why the counts differ
23 things to buy, more apps than that to use.
Looking for something not on this list?
Tell us what you need it to do. We will say plainly whether it exists, whether it is being built, or whether we are the wrong fit.