Apex Scan
In progress
The scanner is the sensor that costs the most to rent, so this one is ours and its results stay in house.
See it
Cloud infrastructure engineered for the systems above. There is no public website to open; it is delivered inside a commission.
Functional scope
A worker that examines files on upload and marks them before any link is minted, so nothing unexamined reaches a portal.
Dependency and secret examination on a schedule, calibrated against a real false positive rate rather than shipped at defaults.
Results written straight into the estate as a sensor, so the scanner is measured by the same rules as everything else.
Runs on your own hardware or your own container, which keeps the artefacts inside your boundary.
Users and roles
Anyone whose product accepts a file from a customer, and anyone who needs to show where their scan results live.
Workflow in practice
Uploads are examined as they arrive. The scheduled passes run overnight. The estate reads the result the same morning.
In production
- No file reaches a portal before it is examined
- The scanner is itself measured as a sensor
- Results stay inside your boundary
Build status
In the shop now, with a date we will name.
Included in every system we build
This is foundation, not a product. It ships inside the systems it belongs to, and its cost is already in their figures.
If a system you are commissioning does not already carry this piece, adding it is a line in your quote, not a second purchase.
It is here so you can see what you are getting rather than take our word for it.
Rails used
Stack
- Container worker
- Postgres
- Signed storage links
Handover includes
- Worker source and container definition
- The sensor contract into the estate
- Calibration notes and the tuning record
- Deployment runbook
Ask about Apex Scan
Tell us how your business runs today and we will show you which systems carry this piece and what they would cost you.