About & trust
Check it before you trust it.
MicroENV runs the thing you're unsure about — a package, a script, a website — inside a sealed micro environment, records everything it does, and has an analyst explain the result in plain language. You get a verdict, the reasons behind it and the raw evidence.
01
Sealed sandbox
Each check gets a fresh container with no access to your machine or our network. Packages and scripts really run; websites are visited by a real browser.
02
Everything recorded
Files touched, processes spawned, network calls attempted, cookies set — captured as evidence, not guessed from the source code.
03
Analyst verdict
An AI analyst reads the evidence and writes the verdict and the why. The evidence is always shown alongside, so you can disagree.
Who is behind it
MicroENV is built and run by Danijel Popović, an independent software engineer in Serbia, who got tired of pasting unknown install scripts into a terminal and hoping for the best.
It is not backed by a security vendor and does not sell data. Revenue comes from the checks people pay for — nothing else.
Not the old MicroENV
The current MicroENV launched in 2026. It is a new, independent product and is not related to the earlier MicroENV developer platform (mock REST APIs, code and project generation, app.microenv.com) that used this domain before.
That earlier service is no longer available, and we cannot help with accounts or projects from it. Anything you read about mock APIs or code generation under the MicroENV name refers to the old platform.
What we keep
Your email, the input you submit and the resulting report, for 7 days. After that they are deleted automatically, and a job page shows “expired”.
The sandbox is destroyed the moment a job finishes. Nothing you upload is executed anywhere else or used to train models.
If you share a report link, anyone with the link can view the summary and download the PDF until it expires. Your email is never part of a shared report.
What a verdict means
“Safe” means the agent observed nothing suspicious during a real run under the conditions it could reproduce. It is strong evidence, not a guarantee — malware can wait for a specific machine or date.
“Suspicious” and “Dangerous” are always backed by concrete evidence you can inspect: the exact file, process, request or rule that triggered it.
Website checks reflect what a visitor from our sandbox saw at that moment. Sites change; re-run before relying on an older report.
Fair use and limits
Only check websites you own or are allowed to check. The browser is rate-limited, respects robots.txt and cannot reach private networks.
Do not upload real secrets. If you did by mistake, rotate them — and email us so we can delete the job early.
Checks that fail refund their credits automatically. Unused credits bought in the last 14 days are refunded on request.
Contact
Questions, a report that looks wrong, a refund, or a site you'd like removed from our checks: hello@microenv.com. A human answers, usually within a day.
Security issue in MicroENV itself? Same address, subject “security” — we'll acknowledge within 48 hours.