Architecture Overview

Antei runs on a hybrid architecture combining service-oriented design with event-driven workflows. This approach enables modularity, reliability, and responsiveness — critical for secure and scalable indirect tax operations.

All services are deployed across Google Cloud Platform (GCP) and Cloudflare, with PostgreSQL as the core data layer.


Core Architectural Principles

  • Modular Service Components — Ingestion, validation, invoicing, reconciliation, and email logic are implemented as independent services.
  • Event-Driven Pipelines — Webhooks and triggers from connected platforms (e.g., Stripe, Gmail) drive real-time workflows.
  • Stateless Serverless Workers — Cloudflare Workers handle extraction, ingestion, email dispatch, and file rendering without persistent state.
  • Structured Background Jobs — Fallbacks, audits, reconciliations, and cron-driven syncs are orchestrated through Xano and PostgreSQL.
  • Data Isolation by Organization — All data is logically partitioned and scoped to ensure security and multi-tenant compliance.
  • Auditability by Default — Every major action is timestamped and stored, enabling traceability and compliance review.

Infrastructure Stack

LayerProviderPurpose
FrontendRetoolPublic-facing app on *.tax.antei.com
Business LogicXanoAuth, orchestration, fallback logic, API routes
DatabasePostgreSQL on GCPStructured relational storage for all primary entities
Background JobsXano CronReconciliation, sync, validation, calculations
Serverless WorkersCloudflareIngestion, extraction, document generation, email
File StorageCloudflare R2PDFs, registration assets, legal documents, logos
Async ServicesRailway, RenderXLSX conversion, fallback retry logic, ingestion helpers

Hybrid Architecture Summary

Antei combines:

  • Service-Oriented Logic (via Xano + Workers) for predictability, reusability, and modular scope
  • Event-Driven Triggers (via webhooks) for real-time sync and responsiveness
  • Cron-based Reliability for reprocessing, reconciliation, and periodic syncs

This allows for a system that is fast where it matters, but reliable and traceable where needed.


Data Flow Summary

  • Data enters via secure endpoints (Workers or Xano APIs)
  • Structured records are persisted in PostgreSQL on GCP
  • File-based assets are stored in Cloudflare R2
  • Processing steps are logged with metadata and timestamps
  • Sensitive data is tagged and scoped based on classification rules

Diagram


Compliance by Design

Our infrastructure stack is built for security, auditability, and scale:

  • All endpoints use TLS 1.2+
  • Hosting partners follow SOC 2 / ISO 27001-aligned controls
  • Per-org access controls enforced at application and database levels
  • High-availability setup with internal observability for job and data health

Next Steps