Architecture Overview
The platform is built with a modern, cloud-native architecture designed for scalability, reliability, and performance.
System Architecture
Data Flow Model
Precog uses an outbound-only network model. All connections are initiated by Precog—no inbound ports are exposed.
Within this outbound model, data flows in two directions:
| Direction | Description | Example |
|---|---|---|
| Pull from sources | Precog connects to your source systems and requests data via their APIs | Precog calls the SAP API to retrieve records |
| Push to destinations | Precog connects to your destination and writes data | Precog inserts rows into your Snowflake tables |
Key points:
- Precog does not accept inbound connections from source systems pushing data to us
- Precog does not expose data for destination systems to pull from us
- You control timing through schedules; Precog orchestrates the connections
This architecture simplifies firewall configuration (allowlist Precog's static IP addresses) and ensures Precog controls when data transfers occur.
Multi-Tenant Design
The platform supports multiple organizations with complete data isolation and security boundaries.
API-First Approach
All functionality is built around a comprehensive REST API, enabling flexible integrations and custom implementations.
Event-Driven Processing
Data pipeline execution is managed through an event-driven system that ensures reliable processing and error handling.
Technology Stack
Frontend
- Next.js: React framework for the user interface
- TypeScript: Type-safe development
- Tailwind CSS: Utility-first styling
Backend
- Supabase: Database and authentication
- PostgreSQL: Primary data store with Row Level Security
- Real-time subscriptions: Live updates across the platform
Infrastructure
- Cloud-native: Designed for modern cloud deployment
- Horizontal scaling: Components scale independently based on demand
- High availability: Built-in redundancy and failover mechanisms