Permissions, not just roles
A fine-grained permission catalog, ready-made templates and team managers. Access to clusters, registries and integrations is granted per team or per person.
Manage Kubernetes clusters, Helm, terminals, Docker Registry and data services in one web console on your own infrastructure. Use AI with the execution controls supported by your provider.
1 user · 1 cluster · no teams
No license key needed. Install and start using Battani.
Works with your existing stack
Platform
Explore the essentials here, then open each guide for workflows, permissions and configuration.
Connect clusters with kubeconfig, test access and share them with users or teams.
Read the guideInspect and manage workloads, network resources, storage and configuration, with YAML editing and bulk actions.
Read the guideFollow live pod logs, open container shells and reach nodes through temporary debug pods.
Read the guideBrowse charts and repositories; install, upgrade, compare and roll back releases.
Read the guideExplore resource relationships and available metrics, with Prometheus and optional Istio traffic data.
Read the guideManage images, repositories, tenant access, quotas and cleanup policies in the included Docker Registry.
Read the guideAI Assistant
Battani’s assistant pulls logs, correlates events, compares Helm revisions and dry-runs manifests. The approval and read-only modes below apply to the Claude flow. The current Copilot flow automatically approves tools.
Explore AI modes and providersData Services · New
Redis, RabbitMQ, Elasticsearch and SQL each have a dedicated console. Configure connections, share access and control write operations with permissions and read-only locks.
Browse keys and values, manage TTLs, and inspect clients, streams and slow commands.
Read the guideExplore queues and topology; inspect messages and manage publishing, bindings and broker operations.
Read the guideInspect cluster health, search documents and manage indices, snapshots and supported lifecycle features.
Read the guideConnect PostgreSQL, SQL Server, Oracle or MySQL; explore schemas, run queries and export results.
Read the guideSecurity and governance
A fine-grained permission catalog, ready-made templates and team managers. Access to clusters, registries and integrations is granted per team or per person.
Authentication, cluster, Kubernetes, Helm, YAML, registry and AI actions land in the audit log, with sensitive fields masked.
Runs without an internet connection on a signed (Ed25519) offline license. Your registry images stay inside too.
Documentation
Installation, everyday operations and administration each have their own page. Find the feature you need and see how it works.
Choose your deployment, install Battani and connect your first cluster.
Installation guideExplore workloads, logs, Helm, topology, registry and each data service.
Workload guideUnderstand users, teams, permissions, audit records and license options.
Installation
With Docker Compose (including a bundled PostgreSQL option) or Kubernetes manifests. The registry ships in the box.
curl -fsSL https://battani.dev/install.sh | sudo sh
Use Battani without a license key or time limit: 1 user, 1 cluster, no teams. Add a license on the same installation when your needs grow.
Free version and licensingIn-app updates: patch the Kubernetes Deployment, trigger a webhook or update in place inside the container, with automatic rollback if the new version fails.
Settings → Updates → Update now
The script checks Docker, writes the configuration with random passwords, starts the services with a bundled PostgreSQL and prints your sign-in details.
Free, with no time limit · No license key needed. Install and start using Battani.
Run it on the server as root. It offers to install Docker if missing; files go to /opt/battani.
curl -fsSL https://battani.dev/install.sh | sudo shWithout curl: wget -qO- https://battani.dev/install.sh | sudo sh
Backs up the database first, then switches to the new version, and rolls back automatically if it does not start.
sudo sh /opt/battani/update.shYou can also update from inside the app: Settings → Updates.
--version 1.2.3, --port 8080, --url https://k8s.example.com, --no-registry. Example: curl -fsSL https://battani.dev/install.sh | sudo sh -s -- --port 8080Run it in PowerShell. It offers to install Docker Desktop with winget if missing; files go to %USERPROFILE%\Battani.
irm https://battani.dev/install.ps1 | iexWith parameters: & ([scriptblock]::Create((irm https://battani.dev/install.ps1))) -Port 8080
Backs up the database first, then switches to the new version, and rolls back automatically if it does not start.
irm https://battani.dev/update.ps1 | iexYou can also update from inside the app: Settings → Updates.
-Version 1.2.3, -Port 8080, -Url https://k8s.example.com, -NoRegistry, -Dir D:\Battani.Pricing
1 user and 1 cluster are free, no license key needed. Paid licenses are priced per user, with no limit on clusters or teams; the AI assistant, Docker Registry and data service modules are included.
Enter the number of users to see the total and its breakdown for the selected billing type. The first users are billed at the base price, every user beyond the threshold at the lower price.
Prices are in USD and exclude VAT. Invoices in Turkey are issued in TRY at the Central Bank (TCMB) USD selling rate on the invoice date. For public tenders and multi-year contracts, request a quote.
Frequently asked questions
Have a question that isn’t here? Write to us and we will get back within one business day.
Battani runs on your infrastructure and stores its application data in your database. Online licenses contact the license server for validation. If you enable an external AI provider, the context needed for your requests is sent to that provider; choose the provider and access settings to fit your environment.
The features are identical. An online license is validated periodically against our license server and can be billed monthly or yearly. An offline license is a signed key bound to the installation for environments without internet access; it is sold yearly and updates are delivered as offline packages.
Your clusters and workloads are not affected and no data is deleted; Battani is only a management layer. If your usage fits the free mode (1 active user, 1 cluster), Battani keeps running in free mode. If there are more users or clusters, only system administrators can sign in, to activate or renew a license or to deactivate users and clusters; everyone else sees a message explaining why. As soon as a renewed key is activated, full use is restored. We contact you about renewal before the end date.
Every installation without an active license can run with 1 active user, 1 cluster and no teams, with no time limit or license key. Data connections are limited to 3 in total and 1 per service type. Add a license on the same installation when you need more capacity. AI uses your configured provider and may incur provider fees.
A user is an active account in Battani (including LDAP users); you license the number of users you need. A license user is a named account; the same account cannot be signed in on two devices at once. Pricing is graduated: users 1–9 are billed at the base price, and every user from the 10th on at the lower price. Paid licenses have no cluster or team limit, and node and pod counts are not limited either. Free use is limited to 1 user and 1 cluster, without teams.
The assistant uses the provider you configure (with your own key). In fully isolated environments it needs a reachable provider endpoint (e.g. an internal Azure OpenAI); otherwise the AI feature stays off and every other module keeps working.
Battani includes dedicated Redis, RabbitMQ, Elasticsearch and SQL consoles. SQL connections support PostgreSQL, SQL Server, Oracle and MySQL. Available operations depend on the service version, permissions and connection settings; the documentation explains each module.
The 30-day trial license includes every module. When it ends, load a paid license on the same installation and carry on; no reinstall needed.
Battani works through the standard Kubernetes API; you can add any cluster you can reach with a kubeconfig. Battani itself can run inside the cluster (with in-cluster configuration) or outside it with Docker Compose. We are happy to verify compatibility with your distribution during the trial.
Let’s get started
Fill in the form and we will talk through your installation scenario, license type and scale. Trial license requests are answered the same day.