Application platform
Xooshe
Kubernetes without assembling an ops stack
Xooshe (خوشه) is how teams run environments, apps, and databases on Kubernetes — on a cluster you already have, or on capacity we host — with backup, uptime, and billing in the same product.
The name
A cluster, in the original sense
In Persian, خوشه is a cluster of grapes — fruit held together on one stem. Xooshe takes that image for compute: environments, apps, and data, kept coherent as one product instead of a pile of consoles.
Two kinds of work
One platform. Two readers.
For people who ship
Connect a cluster, deploy images and data stores the same way every time, restore when something breaks, read the logs, and put Argus on the URLs customers actually hit.
For people who own the product
Fewer vendors and tickets. Staging that does not quietly drift from production. Recovery you have practiced. Wallet, invoices, and support next to the work — so spend and ownership stay explainable.
In one product
The everyday work of running software, in one place
Deploy, data, backup, uptime, and billing usually live in five tools. Xooshe keeps them together.
Clusters & environments
Attach Kubernetes you already run, or start on capacity Xooshe operates. Keep stages and products somewhere you can actually see.
Apps & data stores
Ship custom images and catalog services in the same flow. PostgreSQL, Redis, MongoDB, MinIO, and more sit next to the apps that need them.
Backups & uptime
Schedule backups with a restore path you can use. Argus watches public URLs so you hear about outages before customers do.
Team, wallet & support
Organizations, prepaid wallet, usage and invoices, tickets, and an in-product helper — so ops and billing stay next to the work.
How work happens
From the first environment to a week of ordinary operations
Choose where it runs
Connect a cluster you already have, or start on hosted capacity when you need somewhere to run without standing up infrastructure first.
Ship apps and data
Deploy your images or ready-made services, add databases beside them, scale when you need to, and open a public URL when the product is ready.
Keep it running
Backup rules, logs, Argus on customer-facing URLs, and spend you can see — so production is work, not a scramble.
The dashboard
One place to see what is running
Open the dashboard when you are ready to run something
Start on a cluster you already operate, or on capacity we host. The docs are there if you want the full picture first.