We help you get started.

With containers and AI.

kTailor tailors a bespoke suit for your containers.

Kubernetes Mutation – Surgical Precision at Blazing Speed

Say goodbye to complex DSLs and slow admission controllers. We're excited to unveil the latest architectural leap for kTailor, the ultra-lightweight mutation engine for K8s! We’ve kept the KISS principle but supercharged the engine. kTailor now features a built-in Informer & Cache system, making it faster than ever while maintaining strict security boundaries.

Why kTailor is a game-changer for your cluster:

Zero Learning Curve: No Rego, no complex logic. If you can write a standard ConfigMap, you’re already a kTailor expert.

High-Performance Caching: Thanks to our Go-native Informer, templates are cached in real-time. Mutation latency? Practically zero.

Enterprise Governance: - Use central.templateName for admin-approved, hardened templates (stored securely in the kTailor namespace). - If enabled by config, use local.templateName for developer-driven flexibility within their own namespace.

Zero Dependency: No databases, no external storage. Just Kubernetes-native ConfigMaps. How it works: Simply tag your ConfigMaps with ktailor.io/template: "true". kTailor automatically "stitches" them into its cache, ready to be applied via a simple label on your Deployment.

Real-World Use Cases (No Image/Helm changes required!):

🔹 Database Tunnels: Instant sidecar injection for secure DB access.
🔹 Time Travel: Debug time-sensitive logic with libfaketime on the fly.
🔹 Dynamic Proxying: Inject HTTP proxy settings into legacy workloads without a rebuild.
🔹 Policy Enforcement: Automatically add security contexts or init-containers.

Stop fighting your tools. Start tailoring your infrastructure.

kTailor ist Open Source and published unter the Apache 2.,0 license. Check the first release on GitHub and the kTailor.devdocumentation website.🚀

Need a custom fit? Our team provides expert consulting for implementing kTailor and crafting hardened template libraries for high-security environments like banking and fintech. Let’s streamline your operations!

Time travel for containers

Software development in the financial sector also involves extensive testing — especially with regard to how the software handles time-related issues. Are the accounts calculated correctly at the end of the year? What happens on a leap day?

In the “good old days,” all you had to do was adjust the server's clock to test the software's behavior. In the age of containers, that's no longer possible — systems are far more complex, and tampering with server clocks can throw the cluster out of balance, making operation and testing impossible; it can even destroy the cluster.

Using the open-source software “libfaketime,” containers can be “shifted through time” without requiring any changes to the application, the code, or the image. It is even possible to run tests with hundreds of containers in parallel and “at different points in time.”

At the data center of Finanz Informatik, the central IT services provider for all German savings banks, we successfully integrated a time-stamping process into the CI/CD environment using libfaketime. Read here to learn what a solution in a Kubernetes environment looks like.

A LLM for chemical reasoning. On premise.

In summer 2025 ether0 was released - a large language model for reasoning in chemical science. Too big to run it locally? Not if you know how to do it.

We encapsulated it into a docker image and placed it successfully on a local appliance, running Linux with two standard GPU: The model worked fine on our appliance and answered our questions fluently.

Considering a trial placement? Then please contact us.

A digital lab assistant with speech recognition that follows your every command. Without the cloud.

As part of a proof of concept, we had the opportunity to work directly in a chemical laboratory. The task was to enhance a glovebox with a voice-based digital assistant. All software components had to run on a device in the laboratory.

Using open source components, we transferred the main components – speech-to-text, text-to-speech and the chatbot – into containers on a simple Raspberry PC running the Linux operating system. The user spoke to the assistant via a Bluetooth headset, leaving his hands free for work, while the digital assistant took control of the glove box and carried out the commands given to it.

All this was achieved with 100% local components. No GDPR issues, no lengthy approval processes with the IT department, no hassle with the union.

Just getting the job done.