Skip to main content

Open Source

epilot builds on open source and actively gives back. Our product codebase depends on millions of lines of open source code, and we contribute tools, libraries, and SDKs to the community under permissive licenses.

Public repositories live at github.com/epilot-dev.

Philosophy​

Open source is a core part of how we build software. Our engineering principle Rent over Build means we rely heavily on open source libraries and frameworks, then focus engineering effort on what makes epilot unique.

We publish our own tools as open source when they solve general problems that others face too -- reusable utilities, framework plugins, SDKs, and UI components. This is good for the ecosystem and good for us: external contributions improve quality, public code raises the bar, and developers who know our tools can onboard faster.

Projects We Maintain​

SDKs and API Clients​

ProjectDescriptionLinks
epilot SDK (JavaScript)Typed SDK for all epilot APIs. Full IntelliSense support.GitHub / npm
openapi-client-axiosFramework-agnostic OpenAPI client built on axios. Powers all @epilot/*-client packages.GitHub / npm
openapi-backendBuild, validate, route, authenticate, and mock APIs using OpenAPI definitions. Used across epilot backend services.GitHub / npm

Both openapi-backend and openapi-client-axios are part of the OpenAPI Stack project, created and maintained by epilot's Head of Engineering. They form the backbone of our API-first architecture.

See the SDK documentation for usage details.

Terraform Providers​

epilot publishes Terraform providers on the Terraform Registry for managing epilot resources as infrastructure-as-code. These power our Blueprints system.

ProviderPurpose
epilot-dev/epilot-workflowWorkflow definitions
epilot-dev/epilot-portalPortal configuration
epilot-dev/epilot-roleRoles and permissions
epilot-dev/epilot-dashboardDashboard creation
epilot-dev/epilot-fileFile entity management
epilot-dev/epilot-validation-ruleJourney validation rules
epilot-dev/epilot-notificationtemplateNotification templates
epilot-dev/epilot-custom-variableCustom variables

UI Components​

ProjectDescriptionLinks
concorde-elementsReact component library for epilot Journeys. Used for all Concorde design components (inputs, checkboxes, radios, etc.). MIT licensed, PRs welcome.GitHub / npm

See Custom CSS for details on the Concorde design system and its tokens.

Domain Libraries​

ProjectDescriptionLinks
@epilot/switching-deadlinesGerman energy market switching deadline calculations (GPKE/GeLi Gas compliance).GitHub / npm
@epilot/pricingPricing calculation utilities for epilot price entities.npm

See the Deadlines documentation and Pricing library documentation for usage.

Integrations​

ProjectDescriptionLinks
epilot-app-zapierZapier integration for epilotGitHub
epilot-app-schufaSchufa credit check integrationGitHub

Other​

ProjectDescriptionLinks
engineering-principlesThe 10 core principles guiding epilot engineering.GitHub
docsThis developer documentation site (Docusaurus).GitHub

Open Source We Build On​

epilot's tech stack relies on major open source projects:

LayerKey Technologies
FrontendReact, TypeScript, Svelte, Tailwind CSS, single-spa, Vite, Radix UI
BackendNode.js, Python, openapi-backend, Zod, AWS CDK, AWS SAM
DataDynamoDB, Elasticsearch, ClickHouse
AILangChain
TestingVitest, Playwright
InfrastructureTerraform, AWS CDK

See the full landscape on our Tech Radar.

Open Skies Program​

The Open Skies Program is epilot's initiative to incentivize engineers and employees to contribute to open source and publish technical blog posts. The program reinforces epilot's commitment to giving back to the communities we depend on.

Open Skies rewards two categories of contribution:

CategoryExamples
Blog postsTechnical articles on AI, serverless architecture, SaaS engineering, product design
Open sourceBug fixes, feature implementations, npm libraries, tooling, documentation

All contributions are public and visible — published on the epilot dev blog, open source repositories, or other public channels.

info

Open Skies reflects a core belief: the engineers who build epilot should be recognized beyond our walls. Public contributions grow careers, strengthen the ecosystem, and build trust with customers and partners.

Interested in working on open source and energy SaaS? See open roles on the epilot engineering team.

Contributing​

All projects under epilot-dev accept contributions. To get started:

  1. Find a project on github.com/epilot-dev
  2. Check the repository README for setup instructions
  3. Open an issue or submit a pull request

Licensing​

epilot open source projects typically use the MIT License:

  • MIT, BSD, ISC — Permissive, preferred for most projects
  • Apache 2.0 — Preferred when patent protection matters
love open source