01Establish the boundary
Authorized scope first.
Start with assets your organization owns or has explicit permission to assess.
Opening the external view
AEVRA
External view resolution00%
Authorized external exposure monitoring
Know what the internet can see.
Aevra is being built to help lean security teams understand forgotten public assets, exposed services, and the external risks that deserve attention first.
Product currently in development. Monitoring will require verified ownership or explicit authorization.
- Authorized scope first.Start with assets your organization owns or has explicit permission to assess.
- See what has drifted into view.Aevra is being designed to organize changing public infrastructure into one legible external view.
- Bring priority into focus.The planned workflow will help lean teams move from external observations to the issues that deserve review first.
Illustrative surface model / no live scan data
THE PLATFORM
External exposure, explained as a workflow your team can use.
Aevra is being built for teams that need a practical record of the internet-facing assets they are authorized to monitor. It starts with an approved target, adds public-surface context, and is designed to guide attention toward the changes and findings worth reviewing.
- For
- Security, platform, DevOps, and technical leaders responsible for public infrastructure.
- Produces
- A traceable view of approved targets, external assets, review context, and planned change records.
HOW IT WORKS
A complete route from approved target to meaningful change.
Every planned step is built around one question: what can this team responsibly understand and act on next?
STEP 0101 / 06
Add an authorized target
Enter a domain your organization owns or has written permission to assess. The target is kept visible as the boundary for every later step.
What you receive
A named target record with its authorized scope.
Target: northstar.example
Scope: primary domain
Status: awaiting verification
STEP 0202 / 06
Verify ownership or permission
Confirm the organization can monitor the target before any future exposure check begins. The workflow is designed to make this decision explicit, not implicit.
What you receive
A recorded authorization decision tied to the target.
Method: domain control
Evidence: verification record
Boundary: approved
STEP 0303 / 06
Discover the external surface
Aevra is being built to assemble the public-facing services, hostnames, certificates, and infrastructure context associated with an approved target.
What you receive
A structured external-surface inventory for review.
Public hostnames
Reachable services
Certificate context
STEP 0404 / 06
Organize assets and relationships
Group the observations into an understandable map: which assets belong together, where they are exposed, and where ownership still needs a decision.
What you receive
A clearer record of assets, relationships, and ownership context.
Domain ↔ hostname
Hostname ↔ service
Service ↔ owner
STEP 0505 / 06
Review prioritized findings
Planned prioritization will help turn a long list of observations into a short, reasoned review queue for the people responsible for the target.
What you receive
A review queue with the context needed to decide what to do next.
Why it matters
Affected asset
Suggested next review
STEP 0606 / 06
Monitor meaningful changes
Over time, planned monitoring will make meaningful external changes easier to spot without asking teams to continuously compare raw public records by hand.
What you receive
A focused change record for authorized assets.
New exposure context
Changed asset relation
Review requested
WHAT YOUR TEAM RECEIVES
Not a stream of raw signals. A documented external view.
Approved target recordWhich domains are in scope and why the team is permitted to monitor them.
External asset contextPlanned visibility into public-facing services, records, and relationships.
Review-ready outputPlanned findings and changes with context for the people accountable for the assets.
RESPONSIBLE USE
Authorization is not a disclaimer. It is the first step.
Aevra is being developed for authorized external monitoring only. The workflow is designed to make the boundary visible before observation, review, or any future check.
- Authorization first
- Only customer-owned assets or assets covered by explicit authorization belong in scope.
- Visible boundaries
- The intended workflow keeps the approved target and its scope visible as the work progresses.
- Human review
- Aevra is designed to add context and priority, not replace responsible engineering and security judgment.
- Honest product state
- Verification, scanning, findings, reporting, and monitoring are still under development and are not live today.
PRIVATE DEVELOPMENT
Start by defining what you are authorized to see.
Request early access to follow Aevra as this authorization-first workflow is developed, or sign in if you already have an account.