FerrataApex

Deployment options

Apex runs where your ERP does.

Some companies want Apex hosted and running in a week. Others keep their ERP, their price lists and their margins inside their own network and want Apex beside them. Apex is the same in each: the same tools, the same Approval Queue, the same audit trail and the same write-back to the ERP.

Deployment optionsPick the boundary
  • Hosted by FerrataYour own database and login
  • Your VPCInside your cloud account
  • On-premOn your servers, by the ERP
  • Air-gappedNo outside connection
The same in each
  • Every tool
  • Approval Queue
  • Roles and record scope
  • Append-only audit
  • Write-back outbox
In a private environment, models can run inside it as open-weight models

Four options

Pick the boundary. Nothing else changes.

Hosted by Ferrata
Run in Ferrata's cloud, with your company's data in its own database behind its own login, which can open no other company's.
Your VPC
Inside your own cloud account, under your network rules and your keys.
On-prem
On your servers, behind your firewall, next to the ERP it reads.
Air-gapped
On a private network with no outside connection, for companies whose policy requires it.

The same in each

One Apex, wherever it runs.

01

The same tools

CPQ, RFQs, price lists, sales orders, production, invoicing and revenue, with nothing held back by option.

02

The same controls

Approval Queue, roles from your Ferrata login, and an append-only audit trail.

03

The same write-back

One outbox to the ERP: claimed once, read before write, read back to confirm.

04

Models inside the boundary

In a private environment, the models that read your data can run inside it as open-weight models.

Getting there

From the first call to a first workflow live.

  1. 01

    Choose

    Your IT team and Ferrata's engineers agree the option against your security policy and where the ERP runs.

  2. 02

    Stand up

    Apex is installed inside that boundary, with your own database, login and keys.

  3. 03

    Connect

    The ERP connection is built and checked on your own account, read only first.

  4. 04

    Go live

    A first workflow runs on real transactions, with every write waiting for a person.

FAQ

Deployment options, run end to end.

Where can Apex run?

Hosted by Ferrata, with your company's data in its own database behind its own login, or in your own VPC, on-prem, or air-gapped on a private network. The option is agreed with your IT team against your security policy and where your ERP runs.

Is Apex the same in every deployment option?

Yes. The tools, the Approval Queue, roles, the audit trail and the write-back to the ERP work the same way in each. What changes is only the boundary: whose cloud or servers Apex runs on, and what can reach it.

Can the models run inside our network?

Yes. In your VPC, on-prem or air-gapped, the models that read your data can run inside that boundary as open-weight models, so prices, costs and margins never leave it.

Which deployment option is on which plan?

Hosted runs on every plan. Deployment in your VPC, on-prem or air-gapped is part of Enterprise, with credits and terms set with you.

Who installs and runs it?

Ferrata's engineers, working with your IT team. In your own environment your team controls the network, the keys and the access; Ferrata works inside the rules you set.

See Apex work on your own quote to cash.

Thirty minutes on one workflow, with your own quotes, orders or invoices. You leave with a view of where Apex fits, and an honest answer if the sequencing is wrong and you should fix something else first.

Your pricing, approval and billing rules are your advantage, and they stay yours. Apex is configured to the way you sell, make and bill. You are not handing over a playbook or fitting into a template.