Skip to content
SarvaSuite

Sarva Platform

Early access

Build and extend on top of SarvaSuite.

The foundation the suite is built on, exposed. If SarvaSuite does not do something your business needs, this is where you add it.

Talk to salesSee the whole suite
Sarva Platform/developers/objects · custom object

Custom object · Service contract

contract_nostringunique
accountreference→ acc
start_datedaterequired
sla_hoursnumberdefault 24
renewal_ownerreference→ user

A custom object gets the same API, permissions, workflow triggers and reporting as any built-in record.

Read it back

GET /v1/objects/service_contract
  ?account=acc_8841
  &expand=account,renewal_owner

200 OK
{
  "data": [{
    "contract_no": "SC-0042",
    "account": { "name": "Meridian…" },
    "sla_hours": 24,
    "start_date": "2026-04-01"
  }],
  "has_more": false
}
RESTWebhooksScoped tokensAudit log
Four surfaces

Extend the model, call it, listen to it, build inside it.

Extensions are first-class rather than bolted on. A custom object behaves like a built-in one everywhere in the suite.

Data model

01

Add fields to built-in records, or define entirely new objects. Custom records get the same API, permissions, workflow triggers and reporting as anything shipped in the box.

  • Custom objects
  • Custom fields
  • Relationships
  • Validation rules

APIs

02

A consistent REST interface across every product, with scoped tokens, pagination, expansion and predictable errors.

  • REST API
  • Scoped tokens
  • Expansion
  • Rate limits
  • Versioning

Events

03

Subscribe to record changes and business events, with retries and a delivery log — so your systems react rather than poll.

  • Webhooks
  • Event log
  • Retries
  • Signature verification

Extensions

04

Add screens, actions and integrations that appear inside the products your teams already use, rather than beside them.

  • Application extensions
  • Custom actions
  • Embedded views
  • Developer tools
Sarva Identity

One sign-in, one permission model.

Users, roles and permissions are defined once and honoured by every product. A person who cannot see margin in the ERP cannot see it in a report, an API response or an AI answer either.

Accounts and roles

Define who exists and what kind of work they do.

Granular permissions

Record, field and action level, per role.

Consistent enforcement

The same rules apply in the UI, the API and reporting.

Audit trail

Who changed what, when, and from where.

For implementation partners

Build the vertical, not the plumbing.

Most industry-specific work is a data model, a set of workflows and a handful of screens. The platform is designed so that is all you have to build.

Talk to us about partnering

Configure, then extend

Fields, workflows and permissions before code. Code only where configuration runs out.

Portable work

An extension built for one customer can be packaged for the next.

Nothing hidden behind an integration

Partners use the same APIs the products use.

Inside the suite

What Sarva Platform shares with the rest of SarvaSuite.

These are not integrations you configure. They are the same records, read from different products.

Sarva AutomationCustom objects can trigger workflows and be acted on by them like any other record.Sarva IntegrationsPrebuilt connectors sit on the same API surface you would build against.Sarva IdentityExtensions inherit the permission model rather than defining their own.Sarva DataCustom records can contribute attributes and events to the unified customer profile.
Next step

Start with Sarva Platform. Add the rest when you need it.

Tell us what your team is doing manually today and we will show you where in the suite it belongs.

Talk to salesExplore products