|
| 1 | +--- |
| 2 | +title: Overview |
| 3 | +description: How can Kowabunga sustain your applications hosting ? |
| 4 | +weight: 1 |
| 5 | +--- |
| 6 | + |
| 7 | +{{% pageinfo %}} |
| 8 | + |
| 9 | +This is a placeholder page that shows you how to use this template site. |
| 10 | + |
| 11 | +{{% /pageinfo %}} |
| 12 | + |
| 13 | +## What is it ? |
| 14 | + |
| 15 | +**Kowabunga** is an [SD-WAN](https://en.wikipedia.org/wiki/SD-WAN) and [HCI](https://en.wikipedia.org/wiki/Hyper-converged_infrastructure) (Hyper-Converged Infrastructure) Orchestration Engine. |
| 16 | + |
| 17 | +Market BS aside, Kowabunga provides DevOps with a complete infrastructure automation suite to orchestrate virtual resources management automation on privately-owned commodity hardware. |
| 18 | + |
| 19 | +It brings the best of both worlds: |
| 20 | + |
| 21 | +- Cloud API, automation, infrastructure-as-code, X-as-a-service ... |
| 22 | +- On-Premises mastered and predictable flat-rate hardware. |
| 23 | + |
| 24 | +## Why Kowabunga ? |
| 25 | + |
| 26 | +- **Cost-Effective**: Full private-cloud on-premises readiness and ability to run on commodity hardware. No runtime fees, no egress charges, flat-rate predictable cost. **Keep control of your TCO.** |
| 27 | + |
| 28 | +- **Resilient & Features-Rich**: Kowabunga enables highly-available designs, across multiple data centers and availability zones and brings automated software-as-a-service. **Shorten application development and setup times.** |
| 29 | + |
| 30 | +- **No Vendor-Locking**: Harness the potential of Open-Source software stack as a backend: no third-party commercial dependency. We stand on the shoulders of giants: KVM, Ceph ... **Technical choices remain yours and yours only.** |
| 31 | + |
| 32 | +- **Open Source … by nature**: Kowabunga itself is OpenSource, from API to client and server-side components. We have nothing to hide but everything to contribute. **We believe in mutual trust.** |
| 33 | + |
| 34 | +**A Kowabunga-hosted project costs 1/10th of a Cloud-hosted one.** |
| 35 | + |
| 36 | +## Why do I want it ? |
| 37 | + |
| 38 | +- **What is it good for?**: Modern SaaS products success are tighly coupled with profitability. As soon as you scale up, you'll quickly understand that you're actually sponsoring your Cloud provider more than your own teams. **Kowabunga** allows you to keep control of your infrastructure and its associated cost and lifecycle. You'll never get afraid of unexpected business model change, tariffs and whatnot. You own your stack, with no surprises. |
| 39 | + |
| 40 | +- **What is it not good for?**: PoC and MVP startups. Let's be realistic, if you're goal is to vibe-code your next million-dollar idea and deliver it, no matter how and what, forget about us. You have other fish to fry than mastering your own infrastructure. Get funded, wait for your investors to ask for RoI, and you'll make your mind. |
| 41 | + |
| 42 | +- **What is it _not yet_ good for?**: Competing with GAFAM. Let's be honest, we'll never be the next AWS or GCP (or even OpenStack). We'll never have 200+ as-a-service kind of stuff, but how many people actually need that much ? |
| 43 | + |
| 44 | +## Is it business-ready ? |
| 45 | + |
| 46 | +Simply put ... **YES !** |
| 47 | + |
| 48 | +Kowabunga allows you to host and manage personal labs, SOHO sandboxes, as well as million-users SaaS projects. Using Open Source software doesn't imply living on your own. Through our sponsoring program, Kowabunga comes with 24x7 enterprise-grade level of support. |
| 49 | + |
| 50 | +## Fun Facts 🍿 |
| 51 | + |
| 52 | +Where does it comes from ? Everything comes as a solution to a given problem. |
| 53 | + |
| 54 | +Our problem was (and still is ...) that Cloud services are unnecessarily expensive and often come with vendor-locking. |
| 55 | +While Cloud services are appealing at first and great to bootstrap your project to an MVP level, you'll quickly hit profitability issues when scaling up. |
| 56 | + |
| 57 | +Provided you have the right IT and DevOps skills in-house, self-managing your own infrastructure makes sense at economical level. |
| 58 | + |
| 59 | +Linux and QEMU/KVM comes in handy, especially when powered by libvirt but we lacked true resource orchestration to push it to next stage. |
| 60 | + |
| 61 | +OpenStack was too big, heavy, and costly to maintain. We needed something lighter, simpler. |
| 62 | + |
| 63 | +So we came with **Kowabunga**: **K**vm **O**rchestrator **W**ith **A** **BUN**ch of **G**oods **A**dded. |
| 64 | + |
| 65 | +## Where should I go next ? |
| 66 | + |
| 67 | +- [Concepts](/docs/concepts/): Lear about Kowabunga architecture and design |
| 68 | +- [Getting Started](/docs/getting-started/): Get started with Kowabunga |
0 commit comments