ASTRATIC
Astratic Technologies LLC · Colorado, USA
Astratic Technologies builds consumer software against organised fraud. The engineering underneath it is disproportionate to the category on purpose — and every claim on this site points at something you can open and read.
One product is live. The next are not named here until they exist and can be used.
Check whether a message, link, phone number or photo is a scam. Free, anonymous, no account. It never reports that something is safe — only whether anything known to be a scam was found, and it says plainly that those are not the same claim. A false assurance is the most harmful output a fraud tool can produce.
The checker runs in the browser at viperai.co today. The iPhone app is in TestFlight and has not yet been through App Store review.
viperai.coA fraud tool asks people to trust its judgement. That is only defensible if the judgement is measured, challenged, and written down where it cannot be quietly revised. Five things we build that most consumer app companies do not.
Every architectural decision is written to a ledger as it is made and never rewritten afterwards. When thirty legacy classifications were found to be wrong, the rejections stayed on the record rather than being tidied away.
docs/decisions.md — "rewriting an append-only ledger to look tidier is the failure this system exists to prevent"
Changes run inside scoped observation windows and are compared against the live path without affecting it. A window found to be invalid is closed and its numbers discarded rather than quoted.
observation windows · validity scoping · cumulative metrics across valid windows only
Detections are challenged before they are trusted, and the tests are written to fail if the defect they describe is fixed by accident rather than on purpose.
"a detector that survives its own fix" — classification coverage suite
Whether a run is real traffic or a test is decided and persisted atomically at write time. A client cannot claim its own execution was production, so the metrics cannot be flattered from the outside.
execution_purpose — derived and persisted atomically; precedence, security and persistence under test
Forty-two migrations. Nineteen carry a rollback written alongside them; the older twenty-three predate that practice and are forward-only. When two migrations disagreed with deployed production state, the files were reconciled to the database rather than the database quietly re-run.
backend/supabase/migrations · 42 forward · 19 paired rollbacks