Business
Rules, actors and business services — extracted by AI, confidence-scored, re-runnable as models improve.
READING OLD CODEBASES
Your codebase already knows your business.
Abiktop scans your Java, Node and React code together with your Terraform, Kubernetes and CI config, and distills it into a living enterprise-architecture graph — every business rule linked to the code and infrastructure that runs it.
No spam. One email when we launch.
Business rules linked to code, data and infrastructure
THE PROBLEM
Architecture knowledge decays the moment it’s written down
Every team pays a silent tax for not knowing how its own system works. It shows up as stale wikis, week-long questions and deploys that cross their fingers.
Docs that lie
The diagram was drawn at kickoff. By sprint three it was wrong; by year two it was fiction. Nobody trusts it, so nobody updates it.
Manual archaeology
“What breaks if we change this rule?” means days of grep, reading strangers’ code and interviewing the two people who still remember.
Knowledge walks out the door
The real map of the system lives in a few senior heads. When one leaves, the map leaves too — and the next engineer spends months redrawing it.
Audit panic
“Where does customer data live, and who can touch it?” If the honest answer is a hand-maintained spreadsheet, every audit becomes a fire drill.
Hand-written docs decay toward fiction. A graph rebuilt from code on every commit doesn’t.
HOW IT WORKS
From source code to a queryable corporate brain
One pipeline on every commit — scan, extract, link, impact
Scan
Static analysis parses Java, TypeScript and React into one graph of files, classes, methods and call edges — no AI, no guessing. IaC adapters read Terraform, Kubernetes and Dockerfiles.
Extract
LLMs read the code graph — never raw source or secrets — and pull out business rules, actors and services. Each finding is confidence-scored and kept separate from deterministic facts.
Link
Rules, code, data and infrastructure are joined into four linked layers — business, application, data and technology: one queryable graph, versioned by commit, answerable “as of” any point in time.
Impact
Change a business rule, see every affected service and cluster. Change a line of code, see which rules it touches. Bidirectional, right inside CI.
IMPACT ANALYSIS
See the blast radius before you merge
Abiktop walks the graph in both directions. Change a business rule and see every service, table and cluster it touches. Change a line of code and see which rules need a second look — in CI, not in production.
- CHANGED
- affected
- untouched
1 rule → 2 services · 1 table · 1 cluster
A single rule change propagating through the four layers
THE FOUR LAYERS
An architecture record that keeps itself
Application
Services, classes, methods and the call graph — from deterministic static analysis.
Data
Schemas, tables, buckets and third-party integrations — detected from code and config, secrets redacted.
Technology
Terraform, Kubernetes, Docker and CI/CD — parsed straight from your infrastructure as code.
- Secrets redacted before anything is stored
- Deterministic facts kept separate from AI inferences
- Every node versioned by commit — diffable as-of states
- GraphQL API and graph visualization included
Layer model maps cleanly to TOGAF and ArchiMate — model it in Sparx EA, or keep it live here.
SUPPORTED TODAY
Speaks your stack, not just Java
Code
- Java
- TypeScript
- JavaScript
- React / JSX
Infrastructure as code
- Terraform
- Kubernetes
- Helm
- Docker
- CI / YAML
More adapters ship with every release — tell us what to parse next.
WHAT YOU GET
A corporate brain that does the remembering
Docs that can’t go stale
The documentation is a graph rebuilt from code on every commit — not a wiki page someone owes an update.
Answers in minutes, not weeks
“Which services touch refunds?” is a GraphQL query, not a week of digging through repos and chat history.
Onboarding at graph speed
New engineers explore a living map of the system instead of collecting oral history one coffee chat at a time.
Safer changes, calmer deploys
The blast radius is computed in CI before merge — not discovered in production after deploy.
Audit-ready by default
Every node is versioned by commit. Show auditors the system exactly as it was on any date — “as of” is a query.
Your code stays yours
Secrets are redacted before anything is stored, and the LLM reads the graph — never your raw source.
CONTACT
Tell us what your graph should answer
Monorepo or legacy estate, one repo or two hundred — tell us about your codebase and we’ll show you what Abiktop can map.