maintain.tech

maintain.tech

Autonomous software maintenance, all the way to production

maintain.tech audits your applications, builds the plan that makes them maintainable, carries it out with Claude Code or OpenCode, then ships security patches and minor upgrades on its own, once your tests allow it.

Become a pilot company See the journey
Early-stage ventureWorking alpha by late December 2026
app.maintain.tech · project page
Project page in maintain.tech: readiness score of 36, a five-condition quality gate, per-area scores and a prioritized plan with blocking recommendations.
Screenshot of the alpha on a sample project: score measured by analyzers, quality gate, plan ordered by prerequisites.

55

days to fix a high or critical vulnerability

Average according to Gartner, cited by Snyk in 2026.

The problem

An available patch still needs to reach production

01

Identify the right fix

Assess exposure and check which versions are compatible with the existing code.

02

Prove the fix works

Update the code and run the project’s checks. Teams still have to coordinate the work.

The journey

A readiness plan, then autonomy

Autonomy is switched on project by project, once the quality gate passes. You approve, the platform executes.

01

Audit and prioritized plan

Docker, CI/CD, tests, coverage, versions, dependencies: measured by analyzers, without an LLM. Recommendations ordered by prerequisites, which you can adjust.

02

Tests and mutation testing

maintain.tech writes and runs the missing tests, then checks their effectiveness with mutation testing.

03

CI/CD through production

The platform configures or fixes pipelines, then verifies deployment and rollback.

04

Supported or LTS release

The agent proposes and implements the required migrations, after approval in the interface.

The demo

A patch reaches production, with no intervention

Within the previously authorized scope, with evidence at every step.

01

Detection

Ready project, known vulnerability, patch eligible under the project’s policy.

02

Fix

Isolated branch, dependency update, code changes where needed.

03

Validation

Tests, targeted mutation testing on the changed code, a fresh scan, a green pipeline.

04

Production

Merge, deployment of the validated artifact, health checks, rollback when needed.

Guardrails

Evidence governs autonomy

A

Before the change

Quality gate passed: supported version, effective tests and working CI/CD.

B

Before deployment

Required checks pass on the exact artifact to be deployed.

C

After deployment

Health checks, and rollback to the previous version when needed.

D

When evidence is unclear

Stop with a clear diagnosis. The agent cannot weaken the rules.

Comparison

Today’s tools detect or fix. None ships to production.

maintain.tech doesn’t replace your analyzers: it builds on them to prepare, execute and ship.

Capability maintain.techSonarQubeSnykRenovate / DependabotGitHub Copilot AutofixModerneAI agents (Devin…)

● covered · ◐ partial · – none. maintain.tech: alpha target scope (December 2026). Competitors: public documentation, October 2026.

Ecosystems

Onboarding for each ecosystem

PHPJavaPythonJS / TS / Node
TodayIn-depth audits for PHP and Python, with tests run and coverage measured. GitLab and GitHub, including self-hosted.
NextJava and JavaScript, complex migrations, production signals and a Slack agent.

Plans

Start by seeing where your applications stand

Scans and the dashboard use no LLM, so they stay free.

Free

€0

  • Up to 5 projects
  • Scans of your GitLab and GitHub repositories
  • Portfolio dashboard
  • Quality gate and findings with evidence
  • Rules-based plan

Cloud

subscription · included usage · capped overages

  • Plan prioritized by Claude
  • Changes delivered as merge requests
  • Autonomous maintenance all the way to production

Private workers

custom quote

  • Execution and, when needed, inference in your environment
  • Open models served in your environment (Qwen3-Coder…) through OpenCode
  • The same control interface

Private deployment

later

  • The full platform in your infrastructure
  • Annual license

Next step

Building with pilot companies

A working alpha in 8 weeks

For CIOs and engineering or platform leaders who run several applications in production that need to be modernized, then maintained over time.

Write us

Your address is only used to get back to you about the pilot program. You can also write to contact@maintain.tech.

01

A representative repository

One application from your portfolio, with its real constraints.

02

A defined onboarding scope

What the platform may change, and how far it may go.

03

An available technical owner

To approve the plan and review the first merge requests.

04

A shared metric

Time to a validated patch in production, compared with your current process.