About

What is 1ADK?

1ADK is a small product with one job: keeping a company's understanding of its own software inside the company.

Short answer

1ADK builds and keeps a technical picture of software you own — what it contains, what depends on what, the evidence behind each claim, and what is not known. It works without repository access: your own coding agent produces a structured account of the system, and 1ADK checks it, records it and compares it with the last one. It is built by Mikhail Piskunov and it is new: there are no customer case studies on this site because there are not yet any customers to write about.

#What 1ADK is

1ADK
A service that builds and maintains a technical picture of a software system — its components, their relationships, the interfaces between them, the claims made about them, the evidence behind each claim, and the questions that are still open. The picture is rebuilt whenever the system is analysed again, and every version is kept, so the differences between two points in time are themselves a result.
In plain terms A place where the technical understanding of your software lives, so that it does not only live in one person's head.

The description is deliberately the same one used in the structured data on this page, on the pricing page, and in every profile 1ADK has. A product that describes itself five different ways is a product nobody can quote.

#Why it exists

A software owner can hold every legal right to a system and still be unable to answer the simplest questions about it: what it is made of, what it talks to, what happens if this part stops, who is the only person who knows why it was built that way.

The reason is not negligence. It is that understanding a system is a different asset from owning its code, and only one of the two is stored anywhere. The repository is backed up, versioned and protected. The understanding lives in the working memory of whoever built it, and it leaves when they do — with the notice period, the acquisition, the change of agency, or the reorganisation.

This has become sharper rather than softer as software gets faster to write. A system assembled quickly, partly by coding agents, can reach production while nobody in the company has ever held the whole picture. The code is fine. The understanding never existed in the first place.

The sentence the product is built around

"I want to understand my own system and not depend on the people who wrote it." Everything on this site is a version of that sentence applied to a specific situation.

#What it is not

Being clear about this is more useful than another paragraph about what it does.

  • Not a code reading assistant. A coding agent answers a question now, brilliantly, and holds nothing afterwards. 1ADK is for when the answer has to outlast the person who asked it and be checkable by somebody who did not.
  • Not a documentation editor. Nobody writes pages in 1ADK. The picture is derived from analyses and carries citations; a wiki carries whatever somebody last typed.
  • Not a security scanner. It does not look for vulnerabilities and does not tell you your system is safe.
  • Not an architecture diagram tool. You do not draw anything. If a diagram disagrees with the analysis, the analysis is the thing with evidence attached.
  • Not a consultant. A consultant produces one excellent report on one date. That report begins going out of date on the same date.

If your situation is genuinely better served by one of those, the solution selector will say so. It is allowed to recommend against 1ADK, and it does.

#Who builds it

Mikhail Piskunov

Founder

Builds 1ADK. Has spent the last years working on software systems whose owners could not answer basic questions about them without asking the person who wrote the code.

Technical guides on this site carry an author line for the same reason the product carries evidence: a claim you cannot attribute is a claim you cannot weigh.

#What stage it is at

Stated plainly, because it changes how much weight to give everything else here.

  • The product works end to end. Register, create a project, run an analysis, read what is known, run it again, see what changed.
  • There are no customer case studies on this site, because there are no customers to write about yet. Every example you will see is invented and labelled as invented.
  • There are no testimonials, logos, ratings or usage numbers for the same reason. When there are real ones they will appear with the customer's permission and their name on them.
  • Card payments are not live. Paid plans exist and are enforced; the way to start one today is to ask, and a person replies. The pricing page says this in its own words.
  • There are no security certifications. The security page lists that gap alongside the others.

A new product that pretends to be an established one is easy to catch and hard to recover from. It is cheaper to say what is true.

#How it is paid for

By the people who use it. There is no free tier funded by advertising, no data resale, and nothing on this site is behind an email address.

Payments will be received by FinMV SIA (Latvia), through Stripe. Card payment is not switched on yet — until it is, a paid plan begins with a conversation and nothing is charged before you have agreed to it.

#How to reach a person

info@1adk.com — for anything at all. Somebody reads it.

security@1adk.com — for a suspected vulnerability. See the security page for what to include.

1ADK also exists on linkedin.com, x.com and reddit.com .

Find out what you actually own.

No repository access. No source-code upload. No card.

Build your project map — free