The platform

One platform.
Nine specialised
applications.
Endless possibilities.

FlowZa AI brings together independently built cloud applications, each with its own data, capabilities, and pricing. Connected by a common technology foundation and vision, every product is designed to solve a specific business challenge—without compromising its independence.

Independence

What is common, and what is not

The nine applications have a vendor, a security standard and a regional compliance practice in common. They do not have a database in common. An application does not read another application's customers, stock or ledger, and adopting a second one does not change what the first one holds.

That is a deliberate trade. It means each application can be deployed, priced, upgraded and retired on its own schedule, and that no outage or migration in one is capable of reaching another.

What the nine FlowZa AI applications have in common and what each one holds independently
AspectCommon to all nineHeld by each application
Data—Its own database and its own records
CommercialsOne vendor and one contactIts own pricing and subscription
ReleasesEngineering standardsIts own release train
SecurityTenant isolation, SSO, audit logEnforced inside the application
ComplianceIndia and Gulf expertiseThe statutory engines it needs
APIConsistent conventionsIts own endpoints and credentials

Developers

An API for each application you hold

Every application exposes its own REST and GraphQL API over the records it holds, with the caller's own permissions applied. The conventions are the same across the nine — the same auth scheme, the same pagination, the same error shapes — so a client written against one is familiar against the next. The credentials and the endpoints are separate, because the applications are separate.

  • Custom objects

    Extend an application's schema with your own entities. They inherit its permissions, audit, search and API access automatically.

  • Functions

    Run server-side logic on any record event within the application, with the same execution guarantees as first-party logic.

  • Webhooks

    Subscribe to events from an application and drive whatever you like downstream — including another FlowZa AI application, if that is what you want.

# FlowZa POS. Its own host, its own credentials, its own records.
GET https://pos.flowza.ai/v1/customers/cus_8f21

{
  "id": "cus_8f21",
  "name": "Amara Osei",
  "application": "pos",   // this record lives here
  "basket_count": 34,
  "last_seen": "2026-07-30"
}

A customer in FlowZa POS is a FlowZa POS record. If you also run FlowZa Club and want the two to know about each other, that is an integration you build against both APIs — deliberately, and on your terms.

Coverage

Nine applications.
Six business functions.
What each one covers.

Read a row to see what a single application covers if it is the only one you buy. Every row stands alone — nothing in this table depends on you holding a second application.

Matrix of the nine FlowZa AI applications against six business functions — selling, stock, money, people, field and site, and customer — marking each as a core capability, a supporting capability, or not covered. Each row describes one application on its own; no row depends on any other application being present.
ApplicationSellingStockMoneyPeopleField & siteCustomer
FlowZa Financefinance.flowza.aiSupporting capabilityCore capabilityCore capabilityCore capability—Not coveredSupporting capability
FlowZa LogisPrologispro.flowza.ai—Not coveredCore capabilitySupporting capabilitySupporting capabilityCore capabilitySupporting capability
FlowZa Spa Masterspamaster.flowza.aiCore capabilitySupporting capabilitySupporting capabilityCore capability—Not coveredCore capability
FlowZa Fleetzafleetza.flowza.ai—Not coveredSupporting capabilitySupporting capabilitySupporting capabilityCore capability—Not covered
FlowZa QRForgeqr.flowza.ai—Not covered—Not covered—Not covered—Not coveredSupporting capabilityCore capability
FlowZa POSpos.flowza.aiCore capabilityCore capabilitySupporting capability—Not coveredSupporting capabilityCore capability
FlowZa Clubclub.flowza.aiCore capabilitySupporting capabilityCore capabilitySupporting capabilitySupporting capabilityCore capability
FlowZa RentFlowrentflow.flowza.aiSupporting capability—Not covered—Not covered—Not covered—Not coveredCore capability
FlowZa PMSpms.flowza.ai—Not covered—Not coveredSupporting capabilityCore capability—Not covered—Not covered
Core capabilitySupporting capabilityNot covered

Read along the Club row

Five marks out of six. A club is an unusually complete business in one building — it sells, it holds stock, it bills, it rosters and it books facilities — so the application that runs one has to cover nearly all of it without help.

Read along the RentFlow row

Two marks out of six, and that is the honest answer. RentFlow screens and decides tenant applications. It is a small, focused product, and the table says so rather than dressing the gaps up as something you can fill from elsewhere in the range.

Book a walkthrough →Security and compliance