Skip to content

Getting Started

What is Servanex?

The platform in one page — what Servanex is, what it isn't, and how it's structured.

Servanex is an AI-native platform for modern field service. It replaces the patchwork of FSM, CRM, payments, memberships, and back-office tools with one platform organized as roughly sixteen modules — CRM, lead and opportunity, job and dispatch, pricebook, revenue, ledger, memberships, communications, AI agents, knowledge, workflows, platform billing, notifications, marketing, identity, and audit log.

Every module shares the same data substrate, the same permissions, and the same AI layer. You don’t sync data between tools — you stop using four tools.

The three non-negotiables

Three architectural commitments make Servanex what it is. We don’t violate them.

One action layer. Every write — every dispatch action, every tech tap on the mobile app, every Voice AI booking, every QuickBooks webhook — goes through one validated, permissioned, audited tool registry. Nothing writes to the database directly. This is what makes AI a real co-worker instead of a chat feature: the AI calls the same tools your CSRs do.

Event-driven from day one. Every state change emits a domain event via the Postgres outbox pattern. Workflows, AI agents, sales plays, and integrations subscribe to events. New capabilities ship as a config record and a tool — not a rewrite.

Multi-tenant isolation, defense in depth. Postgres Row-Level Security on every tenant-scoped table at the database. Independent tenant assertions at the action layer on every tool input and output. Redis, Pinecone, OpenSearch, and S3 are all tenant-scoped by key, namespace, or prefix. A cross-tenant leak would require bypassing two independent layers.

What Servanex is not

  • Not a CRM with AI bolted on.
  • Not a transcription service for your existing tools.
  • Not a chat widget pretending to be an agent.
  • Not a low-code platform you have to assemble yourself.