Tech Stack & Architecture
info
epilot is a multi-tenant SaaS platform for energy suppliers, municipal utilities, grid operators, and solution providers. It provides a 360° energy XRM (extended relationship management) to digitize sales, service, and grid processes end-to-end.
Overview
The epilot application consists of:
- The epilot 360 portal — single-spa micro-frontend SPA
- Embeddable Journey Frontends — customer-facing forms and flows
- epilot Portals — white-label self-service portals for end-users, with mobile app support
- Serverless microservices with public APIs
Architecture
epilot runs entirely on AWS in the EU (Frankfurt) region as a cloud-native, serverless platform.
The backend is composed of independent microservices deployed as Lambda functions behind API Gateway. Services communicate asynchronously through EventBridge and SQS. All APIs follow an API-first design — OpenAPI contracts are defined before implementation, powering auto-generated SDKs and documentation.
The frontend consists of multiple independently deployable applications — the epilot 360 portal (a single-spa micro-frontend SPA), embeddable journey frontends, and white-label end-user portals — all built with React or Svelte and sharing the Volt UI design system.
Tech Stack
Frontend
| Technology | Role |
|---|---|
| React | Main UI framework |
| Svelte | Used in select micro-frontends |
| single-spa | Micro-frontend orchestration for the epilot portal |
| Tailwind CSS | Utility-first CSS framework |
| Volt UI | epilot design system (React and Svelte) |
| Capacitor | Hybrid native runtime for portal mobile apps |
| Axios / openapi-client-axios | HTTP client with OpenAPI type generation |
Backend
| Technology | Role |
|---|---|
| AWS Lambda | Serverless compute for all microservices |
| API Gateway (HTTP API) | API routing and authorization |
| Step Functions | Workflow orchestration |
| EventBridge | Event-driven communication between services |
| S3 | File and object storage |
| SQS | Message queuing |
| openapi-backend | OpenAPI-first request handling |
| Zod | Runtime schema validation |
Databases
| Technology | Role |
|---|---|
| DynamoDB | General-purpose data store for microservices |
| Elastic Cloud | Full-text search and indexing for business entities |
| ClickHouse Cloud | Analytical queries, Datalake, workflow data, audit logs |
| Momento | Caching |
Tech Radar
See the epilot Tech Radar for a detailed technology landscape.
Further Reading
- API First — OpenAPI contract-first design and code generation
- Microfrontends — single-spa orchestration of the epilot 360 portal
- SDK — Auto-generated TypeScript SDK for epilot APIs
- Security — Multi-tenant isolation, authentication, authorization, and encryption
- Serverless — AWS Lambda-based microservice architecture
- Continuous Delivery — Trunk-based development, canary and stable release channels
- Design System — Volt UI component library for React and Svelte
- Open Source — Public repositories and community contributions