Skip to content
platform

Concept

Architecture and Security

The trust the AI needs to act on a large operation doesn't come from a well-written prompt, it comes from the infrastructure. CWS Platform governs by architecture: the Commerce Rules Engine, its business rules engine, blocks what isn't allowed, before it happens.

Architecture and Security hero: the Commerce Rules Engine governs by infrastructure and blocks what is not allowed before it happens in the portal.

The layers

Deterministic Core

The Rules-Based Commerce Engine that executes every rule by code, at zero inference cost. It's the governed foundation everything runs on.

AI Agents with Business Guardrails

They consume the Core via MCP (Model Context Protocol), under the same rules as human sellers. They interpret intent, never invent a rule.

Marketplace and network

Multi-seller, buybox and split, with anti-disintermediation. The network operates within the same governance as the Core.

Intelligence and Data

The Analytics Hub and the data dimensions that turn operation into decision. Information to govern with, not just to report.

Autonomy Gradient

AI governance by infrastructure, not by prompt. Every agent action falls into one of three zones:

The Commerce Rules Engine governs by infrastructure: the action within the rule proceeds, and the one outside it is blocked before it happens.
Governance by infrastructure, not by prompt. Trust does not come from a well written prompt: the Commerce Rules Engine blocks what is not allowed, before it happens.

"We have a team that can build this"

You probably do, and we won't argue the point. Programming the pricing rule is the easy part.

The expensive part is access: putting your whole buyer base and your whole sales force on top of that rule without training anyone on the ERP, and without a person in the middle to translate. That isn't a rule, it's a product — a negotiation interface, a catalog by warehouse, a freight engine, an approval machine and a rep app, all of which have to keep evolving alongside the commercial policy long after the first version ships.

And there is a cost that lands on none of those lines: the time until it is live. The rule you build in-house reaches production at the pace of your own backlog.

Coding the pricing rule is one piece; the product is the negotiation interface, the per-warehouse catalog, the freight engine, approval and the seller app.
That is not a rule, it is a product. Negotiation interface, per-warehouse catalog, freight engine, approval machine and seller app, evolving along with the commercial policy.

Infrastructure and security

Infrastructure

The platform runs on AWS with a microservices architecture. AWS holds ISO 27001, ISO 27017, ISO 27018, SOC 1, SOC 2, SOC 3, PCI DSS Level 1 and CSA certifications for the infrastructure CWS Platform runs on. CWS Platform does not hold these certifications in its own name — they belong to the underlying cloud provider.

The platform treats privacy and data protection as a baseline requirement, with native LGPD and GDPR. Access governance and the audit trail follow every decision on price, credit and order.

Data residency

Production data runs on AWS in Brazil today. For US clients, the platform can be provisioned in US AWS regions — data residency is defined during implementation, before any client data is migrated.

Availability

Historical platform availability across all client operations has run above 99.9%, with full months at 100%. This is the observed track record, not a contractual service level; SLA terms are defined per contract.

Operational security

Detailed documentation on backup, disaster recovery and tenant isolation is provided under NDA during technical due diligence.

Three operational security controls: two-factor authentication, access by account portfolio, where the seller reaches only their own accounts, and audit trail.
Who gets in, what they reach and what is recorded. Two-factor authentication on user accounts, access control by account portfolio and audit trail.
A chief technology officer in a moss-green cardigan smiles slightly in the bright corridor of the technology floor, a frosted glass door out of focus behind.

Persona · Chief technology officer

I stopped relying on a prompt to hold back what an agent can do.

In CWS Platform, every agent action falls into a zone of the Autonomy Gradient, under the Business Guardrails of the Commerce Rules Engine.

A legal manager in glasses and a light-grey blazer smiles serenely in the bright legal library, shelves of plain-spined books out of focus in daylight.

Persona · Legal manager

Now I know who requested each action, what was executed and when.

In CWS Platform, access governance and the audit trail follow every decision on price, credit and order, with native LGPD and GDPR.

Frequently asked questions

Does CWS Platform replace the ERP?

No. It's an orchestration layer over the ERP, integrated through APIs and webhooks. The ERP remains the vault for the data; CWS Platform is the commercial manager that governs the negotiation. Publicly associated integrations include SAP, TOTVS, Senior, Sankhya and Microsoft Dynamics.

Where does the data live and how is it protected?

The platform runs on AWS cloud, with a microservices architecture, and treats privacy and data protection as a baseline requirement, with native LGPD (Brazil's data protection law) and GDPR. Access governance and the audit trail follow every decision on price, credit and order.

How is the AI prevented from acting outside what was agreed?

By infrastructure, not by prompt. Every agent action falls into the Autonomy Gradient: green (executes on its own, low risk), yellow (proposes, human confirms) or red (never acts, escalates to the human), under the Business Guardrails of the Commerce Rules Engine.