Governance & Security

Enterprise-grade protection. Control over commercial changes.

Protect sensitive data, define who can act, and apply your approval policies across pricing, workflows and AI.

States from the default Approval Lifecycle, which you can rename. Published means exported, published or pushed, possible only once approved.
  • AssuranceSOC 2 Type IICovers Security, Availability and Confidentiality. The report is provided on written request, under confidentiality.Evidence for your review
  • Security measureEncrypted in transit and at restTLS 1.2 or higher in transit, AES-256 or equivalent at rest, keys in a dedicated key management service.Evidence for your review
  • ProductResource-based access controlsRoles are granted per resource and per operation, inside your organization and its workspaces.How access works
  • SLA commitment99.9% monthly availabilityCommitted in the Service Level Agreement, measured each calendar month, with service credits.Evidence for your review
Data & access

Protect sensitive data. Define who can access it.

Apply access controls across your commercial data, with permissions scoped to the resources each role needs.

  • EncryptionTLS 1.2 or higher in transit; AES-256 or equivalent at rest.
  • Key managementKeys held in a dedicated key management service with restricted access.
  • Environment separationProduction is isolated from development and staging.

Security measures from Annex 2 of the Data Processing Addendum.

OrganizationNorthline
Pricing managerNorth AmericaExample configuration
Pricing manager in the North America workspace: permissions by resource
Resourceviewcreateupdatedeleteexport
Price ListsAllowedAllowedAllowedNot allowedAllowed
Pricing ModelsAllowedNot allowedNot allowedNot allowedNot allowed
DatasetsAllowedNot allowedNot allowedNot allowedNot allowed
ViewsAllowedAllowedAllowedNot allowedNot allowed
Rule EngineAllowedNot allowedNot allowedNot allowedNot allowed

Lifecycle authorityCan Submit. Approve is assigned to Finance.

Pricing analystEuropeExample configuration
Pricing analyst in the Europe workspace: permissions by resource
Resourceviewcreateupdatedeleteexport
Price ListsAllowedAllowedAllowedNot allowedNot allowed
Pricing ModelsAllowedNot allowedNot allowedNot allowedNot allowed
DatasetsAllowedNot allowedNot allowedNot allowedNot allowed
ViewsAllowedAllowedAllowedNot allowedNot allowed
Rule EngineAllowedNot allowedNot allowedNot allowedNot allowed

Lifecycle authorityCan Submit. No lifecycle approvals.

Finance reviewerFinanceExample configuration
Finance reviewer in the Finance workspace: permissions by resource
Resourceviewcreateupdatedeleteexport
Price ListsAllowedNot allowedNot allowedNot allowedAllowed
Pricing ModelsAllowedNot allowedNot allowedNot allowedNot allowed
DatasetsAllowedNot allowedNot allowedNot allowedNot allowed
ViewsAllowedNot allowedNot allowedNot allowedNot allowed
Rule EngineAllowedNot allowedNot allowedNot allowedNot allowed

Lifecycle authorityNamed on Approve and Reject for this pricing model.

Illustrative organization, workspaces and roles. Labels are the product's; your administrators define the roles.

How it works: hosting, sign-in and access
Organizations and workspaces
Your organization keeps its data apart from other customers'. Workspaces partition it inside your organization, for example by region or business unit. A user can hold a role in several workspaces and works in one at a time.
Roles and permissions
Administrators define roles. A role grants operations (view, create, update, delete, export and others) on each resource. Two administrator roles are built in; every other role is yours to define. Individual items can also be shared with named users or roles.
Approval authority
Approval is not a permission. Each step of a lifecycle policy names the users or roles who may perform it, so the right to edit a price list never includes the right to approve it.
Customer sign-in
Sign in with a password or a passkey, or through single sign-on over SAML or OpenID Connect, which can map identity-provider groups to workspace roles. Users can add an authenticator app as a second factor.
Revomo's own access
Revomo staff need multi-factor authentication for administrative access to production. Access follows least privilege with unique user identifiers, and it is reviewed quarterly.
Hosting
Amazon Web Services in the United States, in a multi-availability-zone configuration. The application database is MongoDB Atlas, hosted in AWS. Subprocessors are listed in Annex 3 of the DPA.
Commercial changes

Make commercial authority explicit.

Inspect the applicable policy, required approval and recorded changes before a commercial action moves forward.

Price ListsFittings · Northeast distributor

Price change · Northeast fittings

Fittings cost-plus · 240 items
SubmittedAwaiting approval · Finance

Policy

Lifecycle
Approval Lifecycle · Draft → Submitted → Approved
Applicable check
Approve routes by Change % on each item
ConditionRequired approvalItems
Change % above 5Finance18
OtherwisePricing lead222
Exceptions
18 items over the 5% threshold go to Finance
Effective date
Nov 1, 2026 · proposed on the price list
Release
No export, publishing or push until Approved

History

Lifecycle timeline
WhenActorActionState
Oct 5 · 09:14J. RiveraSubmitDraft → Submitted
Oct 2 · 16:40J. RiveraReviseApproved → Draft
Row history On for this price list
ItemFieldPrevious → newBy
2" PVC couplingList price$4.62 → $4.85J. Rivera
3/4" teeList price$1.18 → $1.24J. Rivera

Dependencies

Depends onDatasetVendor costsData flowRule EngineDistributor tiersFormula referencePricing modelFittings cost-plusInherits
Price listFittings · Northeast distributor
Used byPublishing templateNortheast price book

Illustrative. Three product views shown as one: the lifecycle policy, the change history and Lineage.

  • Policies differ by modelEach pricing model carries its own lifecycle policy, so approval steps can differ between them.
  • History is turned on per objectRow history is enabled on a price list or dataset and kept for the period set there.
  • Dependencies are not reasonsLineage shows what a change relies on and affects. It does not record why a decision was made.
  • Approval is not an outcomeAn approval records who released a change and when. It does not measure the result.

The same controls apply where these changes are made

AI actions

AI can assist. Authority stays defined.

Copilot acts with the permissions of the person using it, and every lifecycle step still follows its policy. Automations run within their creator's permissions.

  • Checked before it runsEach Copilot action declares the resource and operation it needs, and the user's role must allow it.
  • RecordedActions Copilot performs are written to the audit log, marked as Copilot actions.
  • Named steps stay with peopleAn automation cannot perform a lifecycle step that the policy assigns to named people.
Illustrative. The three outcomes explain the checks; they are not product state names.
Integrations & operations

Work within your existing environment.

Connect commercial records and supported outputs through the integration pattern appropriate to your systems.

Connectors named are the ones available today. Other systems connect through the API or files; the method is agreed per system.
  • Availability99.9% monthly availability, committed in the SLA with service credits.SLA, on request
  • Hosting resilienceProduction runs on AWS across multiple availability zones.DPA, on request
  • Monitoring and incidentsHourly updates during a Severity 1 incident, and a root-cause report within five business days.SLA, on request
  • Support coverageStandard Support on business days, 9:00 to 18:00 US Central. Priority Support, if purchased, adds 24×7 response for Severity 1.SLA, on request
Evidence

Evidence for your security review.

Find the documentation your security, legal and procurement teams need to evaluate Revomo.

  • Trust Center

    Public

    Current compliance status and security controls. Policies and the system description are available on request from there.

    Visit Trust Center
  • SOC 2 Type II report

    On written request

    Independent assurance over Security, Availability and Confidentiality. Provided once per calendar year on written request, under confidentiality.

    Request the report
  • Data Processing Addendum

    Request access

    How personal data is processed and protected, including the technical and organizational measures in Annex 2.

    Request the DPA
  • Subprocessor list

    Request access

    Each subprocessor, what it does and where it is located, with notice of changes.

    Request the subprocessor list
  • Service Level Agreement

    Request access

    The monthly availability commitment, service credits, support hours and response targets.

    Request the SLA
  • Subscription Agreement

    Request access

    Ownership and use of your data, security obligations, breach notice, and return of data at the end of the term.

    Request the agreement

A defined path from evaluation to activation.

Scope, data, workflows and success measures are agreed in the Activation & Success Plan before work starts. Standard Delivery is included in the subscription fees for the scope recorded there; bespoke integrations and custom development are scoped separately. Standard Support is included, and Priority Support can be added.

FAQ

Common questions

Where is Revomo hosted, and where is our data processed?

On Amazon Web Services in the United States, in a multi-availability-zone configuration, with production separated from development and staging. The application database is MongoDB Atlas, hosted in AWS. Subprocessors, what each does and where each is located are listed in Annex 3 of the Data Processing Addendum. Contact us to review residency or deployment requirements.

How are permissions managed?

Through roles your administrators define. A role grants operations such as view, create, update, delete and export on each resource, for example price lists, pricing models, datasets and views, inside a workspace. Users can hold roles in several workspaces. Single sign-on can map identity-provider groups to workspace roles. Approval authority is assigned separately, on each lifecycle step.

How are pricing changes and AI actions governed?

By the lifecycle policy on each pricing model. A price list moves from Draft to Submitted to Approved by default, each step names who may perform it, and conditions can route records to different approvers. Nothing is exported, published or pushed until it is approved. Copilot acts with the requesting user’s permissions, and automations stay within their creator’s permissions.

How is our data used with AI?

Your data is used to provide, support, secure and improve the Service. Separately, the agreement permits Revomo to use aggregated and de-identified data, including to train and improve models, only in a form that cannot reasonably identify you, your users or your customers. Revomo-provided inference runs through Amazon Bedrock, a listed subprocessor. Customer-provided inference is not described in the published agreements; raise it during review.

Which integration patterns are supported?

Supported connectors (today Databricks, Salesforce and Google Drive), the Revomo API, and file exchange. Approved price lists can be pushed to Salesforce price books and Databricks tables, and exported or published as documents. Other systems are reached through the API or files. The method for each system is recorded in the Activation & Success Plan.

What happens to our data when the subscription ends?

You can request a copy. For 30 days after expiry or termination you may request your data in writing, in a commercially reasonable format. After that, Revomo may delete it from active systems in the ordinary course. Backups are removed on standard retention cycles and stay protected until then, subject to any legal hold. Aggregated, de-identified data may be retained.

Where can our reviewers obtain documentation?

Start with the Trust Center for current compliance status and controls; its policies are available on request there. The Subscription Agreement, Service Level Agreement and Data Processing Addendum are provided in full on request. The SOC 2 Type II report is provided once per calendar year on written request, under confidentiality.

Put commercial intelligence to work with confidence.

Review how Revomo's access controls, approval policies and operating commitments fit your requirements.

Plate B2 · Series 2026