"Business Logic outlives Infrastructure"
Welcome to the official repository hub of Quatrain Technologies.
We build enterprise-grade, cloud-native, and highly modular frameworks designed to decouple your core business logic from transient infrastructure. Whether you are targeting strict data-sovereignty using on-premise infrastructure or scaling instantly on global Cloud/BaaS providers, Quatrain empowers you to build robust systems with zero vendor lock-in.
The Quatrain ecosystem is organized across specialized repositories to keep concerns completely separated:
| Repository | Purpose | Primary Technologies |
|---|---|---|
| Core | Sibling foundation library packages, adapters, and business logic frameworks. | Bun, TypeScript, PostgreSQL, SQLite, Firestore, Supabase, RabbitMQ |
| CoreUX | Shared UI/UX components, visual styling tokens, and framework-agnostic headless interface controllers. | React, Mantine UI, TailwindCSS, TypeScript |
| CoreApps | Visual designer portals, modeling API gateways, reference applications, and OCI image specifications. | React, Mantine UI, Express, Yarn Berry (v4) Workspaces, Docker/Podman |
| actions | Centralized, reusable GitHub Actions mutualizing CI/CD pipelines. | GitHub Actions, Shell, Node.js |
| apps.quatrain.dev | GitOps recipes, Kubernetes manifests, and Podman Compose deployment scripts. | Podman Compose, Traefik, Kubernetes |
The following diagram illustrates how the various parts of the Quatrain ecosystem interact, from shared composite CI actions to ready-to-run container deployments:
graph TD
%% Repository Blocks
subgraph ActionsRepo ["Quatrain/actions"]
A[reusable CI workflows]
B[prepare-package-json]
C[push-tag]
end
subgraph CoreRepo ["Quatrain/Core"]
D["@quatrain/core (In-Memory Logic)"]
E["@quatrain/types (Contracts)"]
F["Infrastructure Adapters (Postgres, S3, OIDC, AMQP)"]
end
subgraph CoreUXRepo ["Quatrain/CoreUX"]
G["@quatrain/ux (Mantine styling)"]
G1["@quatrain/ux-form (Headless Form controllers)"]
G2["@quatrain/ux-list (Headless List controllers)"]
end
subgraph CoreAppsRepo ["Quatrain/CoreApps"]
H["studio-web (React Canvas)"]
I["studio-api (Modeling Engine)"]
J["api-gateway (Routing & Redis Proxy)"]
K["studio-image (Bundled Production OCI)"]
end
subgraph DeployRepo ["Quatrain/apps.quatrain.dev"]
L["demo.apps.quatrain.dev (Podman Compose)"]
M["Kubernetes (GitOps manifests)"]
end
%% Dependency & Flow Links
A -.->|Automates CI/CD| CoreRepo
A -.->|Automates CI/CD| CoreUXRepo
A -.->|Automates CI/CD| CoreAppsRepo
E -->|Strongly Typed Contracts| D
F -->|Implements Adapters for| D
E -->|Types| CoreUXRepo
CoreUXRepo -->|Provides Components & Controllers to| H
D -->|Local sibling portal link / NPM Registry| CoreAppsRepo
H -->|Interfaces with| I
K -->|Publishes OCI to GHCR| L
K -->|Publishes OCI to GHCR| M
J -->|Secures & routes requests to| H
Our core engineering philosophy is that infrastructure changes, but business rules persist. All database engines, authentication services, object storage providers, and message brokers are written as interchangeable adapters. You can swap an SQLite local setup for a PostgreSQL database or a Supabase Auth setup for an enterprise OIDC provider through clean, environment-driven configurations.
Quatrain is built from the ground up for strict data sovereignty. You can deploy the exact same application code 100% on-premise on custom virtual private clouds using open-source blocks, or on managed BaaS infrastructure without changing a single line of your domain model.
Every contract and interface is statically and strictly typed, ensuring total safety and self-documenting code. Standard types are separated into the @quatrain/types package to facilitate seamless sharing between backend services, worker runtimes, and frontend applications.
To build and run the complete ecosystem locally, clone the Core, CoreUX, and CoreApps repositories as sibling directories:
CODE/QUATRAIN/
├── Core/ # Foundation libraries & adapters
├── CoreUX/ # UI/UX elements & headless controllers
└── CoreApps/ # Dashboard interfaces & local modeling gateway
Navigate to the CoreApps repository. Because CoreApps uses Yarn Berry (v4) Workspaces, running installation will automatically resolve the @quatrain/* sibling dependencies from both your local Core and CoreUX directories using portal-linking:
cd CoreApps
yarn installBoot up the local modeling API and the developer studio frontend concurrently:
yarn devThe Visual Developer Studio will be accessible at http://localhost:4000 (or the port defined in your environment configurations).
To maintain high maintainability across staging and production clusters, all our Dockerfiles/Containerfiles strictly implement the Open Containers Initiative (OCI) annotations:
LABEL org.opencontainers.image.title="Quatrain Service"
LABEL org.opencontainers.image.source="https://github.com/Quatrain/CoreApps"
LABEL org.opencontainers.image.licenses="AGPL-3.0"
LABEL org.opencontainers.image.vendor="Quatrain Technologies"Quatrain core repositories are open-source software licensed under the GNU Affero General Public License v3.0 (AGPL-3.0).
If your organization requires deploying Quatrain components in proprietary closed-source systems or demands custom SLAs, the Quatrain Team provides:
- Commercial Exceptions: Commercial licensing avoiding AGPL-3.0 copyleft terms.
- Architecture Advisory: Assistance in scaling your decoupled adapter configurations.
- Premium Custom Adapters: Custom integration with internal legacy enterprise systems.
For inquiries, contact us at developers@quatrain.com.