Lytebase
Run Applications on
Infrastructure You Control
A repeatable way to operate K3s-based application environments. Plan infrastructure and platform changes, apply them through controlled workflows, and manage common services without stitching together scripts.
Focus
Built around K3s operations
Lytebase currently focuses on repeatable K3s environments, explicit operations, and project-repo driven configuration.
- K3s-based application environments with Rancher for cluster management, Longhorn for storage and Flux for GitOps.
- Plan/apply workflows for infrastructure, runtime, platform with release and node operations the same control plane.
- Project repositories pin environment configuration, encrypted secrets, and catalog snapshots.
- Operations are queued, audited, and run from reviewed project revisions.
A Practical Base for Self-Hosted Applications
Lytebase gives operators one process for planning, applying, and inspecting infrastructure and platform changes.
Every change starts with an explicit plan. Operators can review infrastructure, runtime, and platform changes before anything mutates.
Submit operations through an API or admin UI, enforce policy gates, and run changes from reviewed project revisions.
Lytebase starts with K3s as a lean Kubernetes foundation for cloud VMs, on-prem hosts, or hybrid infrastructure.
Databases, search, storage, ingress, certificates, and identity services are managed through the same platform workflow.
Cluster state reconciles from your Git repository through Flux — pull-based, continuous, and audit-friendly. Lytebase uses it as the standard sync layer between repo and runtime.
CLI and Control Plane
Plan, Then Apply
Core infrastructure, runtime, and platform changes follow a persisted plan/apply workflow. Plans are integrity-checked against config and state before apply. Release, node, and operational commands run through the same control plane as audited operations.
- Persisted plans for infrastructure, runtime, and platform changes
- Integrity checks against config and state before apply
- Release, node, and operational commands via one control plane
- Audited operation events across environments
- Wait and follow event streams from the CLI
$ lytebase rollout plan \
--project-id your-project1 \
--deployment-id your-project1 \
--domain infra \
--commit-sha "$(git rev-parse HEAD)"
$ lytebase rollout apply \
--project-id your-project1 \
--plan <plan-id> \
--wait \
--follow-events
$ lytebase rollout status \
--project-id your-project1 \
--deployment-id your-project1Control Plane
Operations Console and API
Submit operations, enforce policies, and manage approvals through a central API. Work runs from reviewed project revisions in isolated workspaces for reproducible operations.
- Mutation requests validated against project contract
- Policy-gated operations with pause and approval workflow
- Concurrency-scoped by project, environment, runtime, and domain
- Ephemeral workspaces from git archive snapshots
- Admin UI for rollout, operation, and approval monitoring
Plan operation
→ Validate project configuration
→ Queue or pause for approval
→ Run in isolated workspace
→ Stream events and capture artifacts
Modern Web Interface · Operation management · Approval workflows
A Repeatable Path for Teams That Need Control
Lytebase is for teams that want a self-hosted platform foundation without turning every environment into a custom scripting project.
Run Where You Need It
On-prem, cloud-hosted, or hybrid K3s environments without committing to a single managed platform.
Reduce Setup Work
A repeatable base instead of rebuilding the same platform wiring for every environment.
Keep Control
Self-hosted. Your data, your infrastructure, your operations.
Support Serious Workloads
Internal products, automation systems, customer-facing applications, and AI services.
Open Foundation
Built on Kubernetes, GitOps, Helm, Terraform, and Ansible patterns instead of a closed deployment platform.
Run Leaner
K3s keeps the runtime footprint lower than a full Kubernetes distribution while preserving familiar Kubernetes concepts.
Frequently Asked Questions
What makes Lytebase different from managed Kubernetes services?
Lytebase is self-hostable and infrastructure-first. You run it on your own hardware or VMs, without depending on a vendor control plane. The plan/apply workflow gives operators explicit control over infrastructure and platform changes.
What runtimes does it support?
Lytebase currently focuses on K3s-based application environments. Additional runtime support may come later.
What platform services are included?
Lytebase manages services such as PostgreSQL, Traefik, cert-manager, Rancher, Longhorn, and Flux as part of the platform foundation. These are deployed and maintained through the same CLI and control-plane workflows, and can be extended with project-specific Helm charts.
Do I need Kubernetes expertise?
Some DevOps and Kubernetes knowledge is helpful, especially for debugging. Lytebase turns infrastructure, runtime, and platform operations into phased plan/apply workflows, so teams do not have to hand-maintain raw Kubernetes manifests for the standard platform path.
What about data privacy and compliance?
Lytebase is self-hosted, so application data and operational state remain on your infrastructure. The core platform does not require external telemetry or phone-home activation, making it a strong fit for sovereignty, GDPR, or compliance-sensitive environments.
Can teams use it today?
Lytebase is still in development. We are currently testing with early partners and will announce availability soon.
Build on a Platform You Can Operate and Own
If you want modern infrastructure without tying your platform to a hyperscaler control plane, Lytebase gives you a strong place to start.