DE·EN
AI Services
Named work on your codebase, with a boundary.
Each service below states what we touch, what we deliberately leave alone, how many days
it takes, and the one artifact you hold at the end. We work in your repository, remote or
onsite. The models we run are hosted on vogella servers or inside your own network, so your
source code never reaches a public AI provider.
- ScopeStated in and out, before we start
- DurationFixed days, fixed price
- ProofOne artifact, verified, not a slide deck
Java modernization
5 services
Bringing a long-lived Java codebase back to a current, secure, and buildable state, one
bounded step at a time.
3 to 5 daysJava · Eclipse
Unreachable classes, unused constants, orphaned members, and dangling imports, found by an agent and then proven dead by your IDE's own compiler and search index before a single line is deleted.
In scope
- Internal, non-exported code
- Reference search across the whole workspace, not one project
- Registry scan of plugin.xml, e4xmi, reflection and Class.forName sites
- Build and problem-marker diff after every round, repeated until nothing new falls out
Out of scope
- Exported public API: zero references in one workspace proves nothing
- Behavioural refactoring
- Dependency upgrades
Dry run on eclipse.platform.ui: 3,692 lines removed from 148 files, zero compile errors. 38 classes, 49 constant groups, 3 private members, 107 imports, across six rounds. The safety net held back dozens of classes used from other repositories, a class referenced only from another plug-in's plugin.xml, and e4 addons registered only in .e4xmi files.
You getA line-numbered report of every deletion with the evidence behind it, plus the commits. You review a list, not a pull request you have to audit yourself.
Request this service
5 daysJava
Moving a codebase from Java 8, 11, or 17 to Java 21 or 25, with a green build and a passing test suite at every step rather than one large jump at the end.
In scope
- Toolchain, build files, and CI configuration
- Removed and deprecated JDK API
- New compiler warnings introduced by the release
- Mechanical language modernization: records, switch, pattern matching
Out of scope
- Framework major upgrades
- Deliberate behavioural change
- Performance tuning
You getA repository building and testing on the new Java version, with the toolchain and CI updated and every forced change explained in its commit.
Request this service
3 daysJava
A full inventory of what your application actually depends on, which of it carries known vulnerabilities, and which of it has been abandoned upstream, followed by updates in waves.
In scope
- Direct and transitive dependency inventory
- SBOM, CVE scan, and license review
- Updates in waves with a green build after each
- Replacement of abandoned libraries
Out of scope
- Major framework migrations
- Code changes beyond what an update forces
You getAn SBOM, a triaged CVE list with a decision per entry, and the update commits, each wave verified by a green build.
Request this service
5 daysJava
Coverage on the code you are about to change, not an average across the repository. Characterization tests first, so the behaviour you have today is pinned down before anyone touches it.
In scope
- Coverage baseline and the areas worth covering
- Characterization tests for existing behaviour
- Agent-generated tests, reviewed line by line with your team
- Mutation testing as the real quality signal
Out of scope
- Rewriting production code beyond extracting seams
- Building end-to-end or UI test infrastructure from scratch
You getReviewed tests in your repository, a coverage baseline and delta, and a mutation score that shows the tests actually assert something.
Request this service
3 to 5 daysJava · Any stack
Making the build trustworthy again: the same inputs produce the same result, failures mean something, and nobody reruns a job hoping it turns green.
In scope
- Flaky test identification and fixes
- Build time reduction and caching
- Reproducible builds
- Quality gates on pull requests
Out of scope
- Migrating to a different CI provider
- Infrastructure procurement
You getA reproducible build, a named list of fixed flaky tests, a measured before and after runtime, and quality gates wired into your pipeline.
Request this service
Eclipse RCP and plug-ins
2 services
We maintain parts of the Eclipse Platform itself, so these are the codebases we know from
the inside.
5 to 10 daysEclipse RCP
Bringing an Eclipse RCP application to the current Eclipse release and a current Java version, in waves, with a launchable application after every single wave.
In scope
- Target platform update in waves
- Replacement of removed and deprecated platform API
- Product, feature, and launch configuration
- Current Java version for the product and its build
Out of scope
- Eclipse 3 to Eclipse 4 rewrite
- User interface redesign
You getA product that builds, launches, and passes its tests on the current Eclipse and Java release, with each removed API replacement documented in its commit.
Request this service
5 to 10 daysEclipse RCP
Moving an Eclipse 3 application onto the Eclipse 4 application model and dependency injection, incrementally, with the compatibility layer carrying whatever has not moved yet.
In scope
- Application model and dependency injection
- Parts, handlers, and commands
- Incremental migration behind the compatibility layer
Out of scope
- Full user interface redesign
- New features
You getAn application on the e4 model with a documented migration path for the parts we deliberately left on the compatibility layer.
Request this service
Engineering practice
4 services
Work that changes how the team builds, rather than what the codebase contains.
2 to 3 daysAny stack
A review agent on your pull requests that has learned your house rules from your own review history, tuned until its findings are worth reading.
In scope
- Agent wired into your existing CI
- House rules derived from your review history
- False-positive tuning on real pull requests
Out of scope
- Replacing human review
- Blocking merges without team agreement
You getA review agent running in your CI, its rules committed to the repository, and a written team convention for what it may and may not block.
Request this service
3 to 5 daysAny stack
Turning the workflows your team repeats by hand into agent skills, and connecting the agent to your internal tools through MCP so it works with your systems, not around them.
In scope
- Skills for your repeated workflows
- MCP servers for your internal tools
- Context files and prompts, reviewed and committed
Out of scope
- Building the internal tools themselves
- Operating the AI infrastructure long term
You getSkills and MCP integrations committed to your repository, with the context files and prompts that make them work.
Request this service
3 to 5 daysFlutter
Bringing a Flutter app back to current: dependencies, lints, dead code and unused assets, and enough widget tests that the next upgrade is not a leap of faith.
In scope
- Dependency and SDK upgrades
- Dead code, unused assets, and lint cleanup
- Widget test coverage on critical flows
Out of scope
- Redesign or new features
- Store submission and release management
You getAn app on current dependencies with a passing analyzer, a smaller bundle, and widget tests around the parts that break most often.
Request this service
2 to 3 daysAny stack
A branching model that matches how often you actually release, with review rules and protection that hold it in place.
In scope
- Branch model matched to your release cadence
- Review rules and branch protection
- Repository size and history cleanup
Out of scope
- Migrating between hosting providers
You getA documented branching and review model, configured protection rules, and a repository whose history and size no longer get in the way.
Request this service
Nothing here fits?
These are the engagements we run often enough to scope and price up front. If your case
sits between two of them, or is larger than any of them, tell us what the codebase looks like
and where it hurts. You get back a scope, a duration, and a deliverable in the same form as
the cards above.
For a longer programme across a whole codebase, see the
Java modernization workshop.
Describe your case
Or reach us directly: sales@vogella.com
· +49 40 7880 4360
