Subscription with us
You subscribe to Batchmaker, we run it on W-Make servers. Rollout, backup, updates and monitoring are ours. The fastest route into live operation.
Operations and security
The application runs where your data is meant to stay.
Production data does not leave the plant just because a piece of software is new. Location, reachability and integrations are your decision, not the architecture's.
Three routes
You decide who runs the server.
Your server, our administration
The application runs in your building, on your hardware. Operation, backup and updates are ours. The data stays in the plant.
Your server, your hands
Installation is one Docker Compose call. You run it yourself, we supply images, migrations and the documentation for both.
How it runs
Isolated, frugal, and not on the open net.
Isolated in a container
Every application runs in Docker, separated from the rest of the system, on Windows, Linux and macOS. Where an orchestrator exists, the same application runs under Kubernetes.
Not reachable from the web
By default the application only answers inside your own network. Outside access exists if you explicitly want it, and only then.
The outage is planned for
If the server goes down, the shift keeps working in an offline copy. Reconciliation follows once the server is back. No day stops.
Backups without being asked
Automatic backups belong to operation, not on a task list. Restores are verified, not assumed.
Frugal with resources
The footprint is small enough for hardware you already own. Getting started needs no new server room.
AI only where it is allowed
Connecting to AI systems is possible, locally in the plant or with an external provider. Which one applies is your decision, not a default.
Quality and traceability
What ships can be checked.
Tests ship with the software
Every application comes with tests, including the edge cases where a process on the floor actually breaks. A green run is not a promise, but it is a condition.
The history stays visible
You see what changed, when and why. Updates are announced and described, not applied quietly.
AI tools under fixed rules
I develop with AI tools and agents, under rules written down in the project. Client data does not go into a model, neither for testing nor for explaining.
Servers and agents from practice
Server administration and running networked agents are part of my daily work. That is why operations come before the interface here.
30-min analysis · free
Describe the process that's breaking today.
If you want to know what this looks like inside your network, describe your environment briefly.
Describe the flow that currently ends in copies, side calculations or quiet corrections. I reply within two working days and will honestly tell you whether I can take the case.
- ✓Reply within 2 working days
- ✓Honest assessment of whether I can take the case
- ✓No slide deck needed, just understanding of the flow