Legacy modernization
The API becomes the product
A modern web frontend is great. But the frontend is no longer the differentiator. What really matters is this: In the future, software products will be deeply embedded into agentic workflows. Instead of humans clicking through screens, AI agents will call APIs, execute processes, and make decisions. If you do not make your product automatable, it will be replaced by one that is.
What we deliver
1. The modern stack
Migration from legacy technologies (Clipper, Visual Objects, X#, Delphi, VB6, etc.) to a modern architecture:
Backend:
- MS SQL Server or PostgreSQL
- Web API with ASP.NET Core
- Entity Framework Core (code-first or database-first)
- Authentication & authorization via an STS (Security Token Service) using OpenID Connect / OAuth 2.0
- Optional: DMS module, workflow engine
Frontend:
- Blazor (Server or WASM) or Angular
- Responsive, modern UI components
- Progressive Web App (PWA) capabilities
Infrastructure:
- Docker containers
- Kubernetes orchestration (optional)
- CI/CD pipelines (Azure DevOps, GitHub Actions)
- Monitoring (OpenTelemetry, health checks)
2. The API as a product—our differentiator
This is where our modernization process stands out from other providers. We do not just deliver a backend and frontend. We deliver the automation ecosystem that ensures your modernized product remains relevant in an AI-driven world:
CLIs (Command Line Interfaces)
Command-line tools that can control your software remotely. This is not just a developer toy, but the primary interface for AI agents.
Example of a modernized ERP:
# CRUD-Operationen
appfact customer list --filter "city=Köln"
appfact customer create --name "Mustermann GmbH" --city "Köln"
appfact article search --sku "ART-*"
# Geschäftsprozesse
appfact invoice run --period 2026-03 --dry-run
appfact sepa generate --due-date 2026-03-15
appfact receivables list --min-amount 5000 --dunning-level 2
# Reporting
appfact report open-items --format json --anonymize
MCP Server (Model Context Protocol)
An MCP server that gives AI agents structured access to the software. This allows any MCP-compatible client (such as Claude or custom agents) to use your software—complete with permission checks, audit trails, and security guarantees.
Skills
Documented operating instructions written in Markdown that describe exactly how to use the CLI or Web API for specific tasks. Skills act as the bridge between “what the user wants” and “which API calls are required.”
3. What this means for the end customer
A company using your modernized software can simply say in Claude:
This is not science fiction. This is exactly what happens when an API is automatable and has skills that know how to use it. Without our modernization: An administrator clicks through 15 different screens, exports the data to Excel, and manually builds a PowerPoint presentation. With our modernization: One sentence. Five seconds. Done.