Infrastructure chosen for the system, not for the slide.
Hosting is designed around who uses the product, the data it needs, the availability required and the integrations. Architecture varies by product and by contract. The standards below apply to all of them.
What applies to every product.
Hosting regions
Site and products served from the São Paulo region. Database region chosen per project, in Brazil when the contract requires it.
Recovery
Automatic backups and point-in-time recovery for the database, per the plan contracted with the provider. Objectives written into the order where criticality demands it.
Monitoring
Errors and failures go to Sentry with alerts. Each product has a responsible person and an escalation path.
Retention
Retention periods and deletion flows designed for the LGPD and for what the customer's contract agrees.
Who operates each layer.
The same services appear in the subprocessor list on the compliance page. None was chosen for fashion: each one solves a layer we should not be operating alone.
Architected to be answerable for.
In custom systems the infrastructure follows the same standard until the contract asks for something else: a dedicated project, a specific region, private-network integration. Whatever changes is documented and has a named owner on both sides.
Want to know where your data will run?
Tell us the residency, availability and integration requirements. We reply with the proposed architecture and what it costs to operate.