Companion لبيتك الرقمي.

The kombify AI Platform is the AI side of kombify, for people who come for the assistant itself, with or without a homelab. It powers the Companion: knowledge, memory, specialist agents and the tools they use.

You work with it in Companion Studio in the browser, and kombify Workbench is built to bring it to the desktop. It is built for autonomous work: agents plan, use tools, check their results and carry tasks forward. Your knowledge and conversations stay yours, and you choose the models it works with.

• All kombify products

The Companion is your point of contact across kombify. Whatever product you use, the Companion is who you talk to, by text or by voice, and Kubi, the little cube, opens it on the web.

It is built to know you and your IT: you set the goal, and it plans, uses your connected systems and coordinates specialist agents for personal tasks, paperwork and your homelab. On your phone, the kombify Companion app is built to carry it and let you pick the Experience you came for.

The Companion is optional. The rule is that everything it does for your homelab runs through controls you can also use yourself.

• All kombify products

No. StackKits and Techstack are a complete way to define, set up and run your homelab yourself, with no AI involved. Every product control works directly.

When you want help, the Companion is built to be there: ask a question, let it explain a change or hand over a task. You decide how much you delegate, and what you build never depends on it.

• StackKits overview
• Techstack overview

You can use the models kombify provides as part of your plan, or connect your own key from an AI provider you already use. The platform works with the supported models you choose.

Usage on your own key is billed by your provider and does not count against the AI budget of your kombify plan. The models kombify provides draw on that budget.

• Billing in kombify Cloud

You stay in charge of what the Companion may do. It is built to work through the same product lifecycle you use yourself, and it never receives more authority than you have.

The rule is that a change to your homelab is planned before it runs and recorded after it runs, whoever starts it. You choose which work you hand over, and each change leaves a record you can follow.

• Review, apply and verify
• Identity and security behavior

Yes. StackKits ships an MCP connector named stackkit, so an MCP client such as a coding agent works with your homelab through the same lifecycle as the command line. Documentation and diagnostic tools are available by default; tools that change anything need an explicit write mode and your approval as the owner.

SpeechKit includes speechkit-mcp and a command line tool, so an agent can inspect the framework, scaffold starters and operate a SpeechKit server.

• StackKits MCP connector
• Build with SpeechKit