- What does “truly open source” mean here?
- Everything we build is Apache 2.0. No open core, no source-available license, no features held back for a paid edition. You can change it, host it, and even sell it on a hosting service that competes with ours. That license will never change.
- How is the hosted version priced?
- Operating cost plus a fixed margin of 33%. The operating costs are strictly the server costs, direct tooling needed to run a reliable server environment and licensing costs (certifications as well as third party connectors) needed to run the service. The economies of scale will ensure that as Klopt grows, your prices will go down. Prices are adjusted on the 1st of each month and a public cost report is published along with it.
- How is development funded?
- We rely on open source contributors as well as sponsors, donations and public innovation funding to fund the development of our products.
- Can I self-host?
- Yes, and you can move in either direction. Start hosted and move to your own infrastructure, or the other way around.
- Who owns my data?
- You do. It is fully exportable at any time, in formats you can actually use elsewhere.
- What do “API-first” and “AI-first” mean in practice?
- Every capability in the product is available over the API; the interface we ship is one client among others. For AI that means an MCP server today, so your own agents and tools can work with your data directly.
- Why start with bookkeeping?
- Because it is one of the hardest places to start. Bookkeeping is complex and legally constrained, which is exactly why it has stayed on legacy systems while other software was disrupted. Domain experts, not just developers, are needed to get it right.
- Is it a fit for a large organization?
- That is the goal: from SME to Enterprise, with features, automation and security comparable to the incumbents. As we roll out the hosted version we will look into ISO and SOC 2 certification. We would rather hear about the requirements you cannot compromise on than guess at them.