Skip to content
GitHub stars
Kubernetes Automation

Automate Resource Provisioning from Your Database

Sync Kubernetes resources with your existing data. Works alongside your current GitOps workflowβ€”no migration required.

Works with
Lynq Dashboard - Topology View
Topology View

See It in Action

Watch how Lynq Dashboard visualizes the relationship between Hub, Form, and Node in real-time

When to Use Lynq

Perfect for dynamic, data-driven infrastructure needs

🏒

SaaS Tenant Onboarding

Customer signs up β†’ Tenant environment ready in seconds

Like SlackNotionAtlassian
Signup→DB Record→Lynq→Namespace + Resources
πŸ”¬

PR Preview Environments

Every pull request gets its own isolated environment

Like ChromaticCypressVercel
PR Created→DB Record→Lynq→Preview Env→Auto Cleanup
☁️

Multi-Cloud Resources

Provision AWS, GCP, Azure resources per tenant

+ Crossplane
DB Record→Lynq→Crossplane CRs→RDS, S3, Route53
πŸ”„

GitOps-Managed Tenants

Version control your templates, automate from data

+ Argo CDFlux
Git Commit→Argo Sync→Lynq→Data-Driven Nodes

Built for Safety First

Enterprise-grade safeguards built into every layer

πŸ›‘οΈ

ConflictPolicy: Stuck

Default behavior never overwrites existing resources. Your cluster stays safe.

πŸ”’

DeletionPolicy: Retain

Keep resources even after cleanup. Perfect for data you cannot afford to lose.

🎯

Dependency Graph

If one resource fails, dependents are automatically skipped. Failures stay isolated.

☸️

Server-Side Apply

Kubernetes-native conflict resolution. Built-in drift detection and correction.

How It Works

Three CRDs work together to turn database records into Kubernetes resources

πŸ—„οΈLynqHub
β†’
πŸ“‹LynqForm
β†’
🎯LynqNode
β†’
☸️Resources
MySQL
DatabaseMySQL Records
Lynq
LynqOperator
Kubernetes
KubernetesResources
Deploy
Service
Ingress
Secret
Sync
Apply

Find Problems Instantly

Problem Mode highlights failed nodes and automatically expands the tree to show their parent Hub and Form. No need to scan through hundreds of resources or run complex kubectl commands.

πŸ”΄Failed nodes are highlighted in red
πŸ“ŠProblem count badges on each level
🌳Auto-expand to problem sources
⚑Real-time status updates
Problem Mode - Failed nodes highlighted

Why Teams Choose Lynq

A complete platform for database-driven infrastructure provisioning

πŸ—„οΈ

Database as Source of Truth

Manage infrastructure with familiar SQL. Changes are tracked, rollback is easy.

πŸ“‹

Template-Based Resources

Same patterns as Helm and Kustomize. 200+ Sprig functions built in.

πŸ”„

Server-Side Apply

Built-in conflict detection. No surprise overwrites. Automatic drift correction.

πŸ“Š

Visual Dashboard

Topology view, problem mode, and detailed status. See your infrastructure at a glance.

🎯

Dependency Graph

If one resource fails, dependents are automatically skipped. Failures stay isolated.

πŸš€

Safe Rollouts

Control blast radius with maxSkew. Bad changes affect only N nodes, not your entire fleet.

Works With Your Existing Tools

Add Lynq to your workflow without replacing anything

πŸ”„Argo CD / FluxUse GitOps for Lynq CRDs themselves
☁️CrossplaneProvision cloud resources per tenant
🌐External DNSAutomatic DNS for each node
πŸ“ˆPrometheusBuilt-in metrics and alerts

Lynq doesn't replace your CI/CDβ€”it adds a data-driven automation layer.

Complete Visibility

Overview page shows Hub, Form, Node status at a glance with interactive charts

Dashboard Overview

Start Small, Scale Confidently

Begin with a single namespace. Expand when you're ready.

3

CRDs

Retain

DeletionPolicy

Stuck

Safe Default

200+

Template Funcs

Released under the Apache 2.0 License.
Built with ❀️ using Kubebuilder, Controller-Runtime, and VitePress.