Legacy, understood. Then modernized.
Stratum turns a legacy codebase into a validated cloud-native application through one product that deepens in four phases: understand what the system does, plan the migration, protect behavior with generated tests, then transform it, step by step, with evidence on every claim.
Archaeologist · Map every module, dependency, table and business process into one knowledge graph with evidence.
Archaeology report
legacy-java-billing
Technical debt
HighCore revenue components
Highest risk area
Payment processing
Java 8 · Spring 3 · JDBC/Oracle · SOAP · 48,213 LOC · sample, not a real scan
Built for teams running
How it works
One product that deepens in four phases
Every phase reads from and writes to one knowledge graph per scan, so the plan you approve is the plan that ships.
Phase 1 · Understand
Archaeologist
- The question
- What does this system actually do, and where is the risk?
- Deliverable
- Archaeology Report: knowledge graph, domains, business processes, modernization score and risks, each with file-and-line citations.
- For
- CTO, VP Engineering, PE diligence teams
Phase 2 · Plan
Migration Planner
- The question
- What do we keep, replatform or rebuild, and in what order?
- Deliverable
- Target profile, dispositions map, strangler-fig sequence, cost model with scenarios and an exportable playbook.
- For
- Head of Platform, modernization lead
Phase 3 · Protect
Test Generator
- The question
- How do we change it without breaking what pays the bills?
- Deliverable
- Characterization test suites (unit, integration, golden) compiled and run in a sandbox, plus a safety score per module.
- For
- Engineering managers, QA leads
Phase 4 · Transform
Modernizer
- The question
- Can we ship the change safely, step by step?
- Deliverable
- Verified change sets, cloud artifacts (Dockerfile, Helm, Terraform) and pull requests with migration notes.
- For
- Platform teams, SI partners
Archaeology report
What you get back from the first scan
A report a CTO can act on and a diligence team can trust: a scored, cited picture of what the system does and where it will fight you.
Complexity index
0Technical debt
HighCore revenue components
Highest risk areas
Lines of code
0Files
0Modules
0Endpoints
0Tables
0Dependencies
0Score components
weight · score- Runtime currency20 · 28
Java 8 (public updates ended), Spring 3.2, Tomcat 7
- Architecture coupling20 · 39
3 dependency cycles; billing ↔ payments ↔ subscription
- Dependency health15 · 44
log4j 1.2.17, commons-collections 3.2.1, 6 CVEs
- Test safety15 · 22
11% of modules have tests; billing has none
- Data portability15 · 47
23 Oracle-specific queries, 4 stored procedures
- Knowledge risk10 · 58
Bus factor 1 on billing (git blame)
- Infra portability5 · 61
Hard-coded hosts in 3 properties files
System summary
86%A monthly billing platform for subscription products. Subscriptions are rated by a nightly InvoiceJob, taxed through a TaxCalculator with hard-coded regional rules, and settled through a SOAP payment gateway. Revenue-critical logic is concentrated in two modules that have no automated tests.
Platform
Built to be trusted with the system that pays the bills
A deterministic analysis engine does the structural work. Models only summarize, label and propose on top of it, and everything they say is cited.
01
Evidence on every claim
Every summary, domain, risk and process points at file paths and line ranges and carries a confidence. Unparsed files are listed, not hidden.
Invoices are rated by a nightly job that applies regional VAT rules before persisting.
02
Runs anywhere
Use the hosted service or run the VPC runner inside your own cloud so source never leaves your network. Same product, same report.
isolated per-org storage, encrypted at rest
engine, worker and sandbox inside your cloud
Your code is never used to train models. Secrets are encrypted with Fernet and never returned unmasked.
03
Model-agnostic
Bring your own keys or run local models. Route each workload to the provider that fits, from frontier models to Ollama and vLLM on your hardware.
Bulk, synthesis, planning, coding, chat and embeddings can each use a different provider, with fallbacks and a daily budget.
Pricing
Start with one scan. Grow into a program.
Pay per scan while you evaluate, or move to a yearly plan when the whole team needs the full pipeline. No monthly toggle, no seat games.
Free
open source or under 50K lines
Try the Archaeologist on a small or open-source codebase.
- Full archaeology report
- Knowledge graph explorer
- Ask-the-codebase chat
- Bring your own model keys
- Community support
Team
Most popularper scan, sized by lines of code
A cited, scored report for one system, when you need it.
- Everything in Free
- Codebases up to 2M lines
- Exports: Markdown, HTML, DOCX, PDF
- Migration Planner playbook
- Email support
Business
per year
Unlimited scans and the full four-phase pipeline for one team.
- Everything in Team
- Unlimited scans and re-scans
- Test Generator with sandbox runs
- Modernizer change sets and PRs
- Role-based LLM routing and budgets
Enterprise
per year
For portfolios, regulated environments and SI partners.
- Everything in Business
- VPC runner in your own cloud
- SSO and SCIM
- Audit log and data retention controls
- Dedicated support and onboarding
Assessments
Fixed-scope engagements, delivered on the platform
Priced per system. Every deliverable is produced by the product, so you keep the workspace after the engagement ends.
Diligence Brief
$10–25K
A read-only archaeology of a target's codebase in days: score, risks, key-person exposure and a modernization estimate for the deal team.
Modernization Assessment
$40–75K
Full archaeology plus a target profile, dispositions and a costed strangler-fig sequence with scenarios, reviewed with your architects.
Program Playbook
$75–100K+
The assessment, a generated safety net of characterization tests and the first verified change sets, packaged as a program plan.
FAQ
Questions buyers ask before the first scan
Security, accuracy, scope and what the numbers mean.
Legacy, understood. Then modernized.
Start with an Archaeology Report. Decide with evidence.
Upload a ZIP or connect a repository. The first report on a small or open-source codebase is free.