ArcVeylEV CHARGING SECURITYJoin the conversation ↗

PRE-RELEASE / EVIDENCE-LED SECURITY

Understand what changed.
Know where to look.

The investigation and monitoring workspace for EV charging infrastructure. Bring charger, network, OCPP and firmware evidence together—so your team can diagnose problems and assess security risk.

Evidence first. Confidence earned.

ARCVEYL / SIGNAL EXPLORERILLUSTRATIVE
!
Change is a signal. Context is the answer.

Connection · Configuration · Firmware

Concept visualization. No live devices are connected.

01 / Observe the change02 / Understand the evidence03 / Prioritize the response

THE CONNECTED ATTACK SURFACE

Five places to look.
A clearer way to investigate.

Explore potential failure points and the evidence that could expose them. This is a reference architecture, not a scan of your equipment or a finding against any manufacturer.

INTERACTIVE SYSTEM MAP
↔LOCAL LINK
↔OCPP / TLS
ADDITIONAL CONTROL & UPDATE PATHS → CHARGER
AUTHORIZED TELEMETRY
ArcVeyl evidence reviewAnalysis layer · not an inline gateway
● Selected investigation pointIllustrative paths · actual topology varies

TRY THE THINKING

Same change.
Different consequences.

Review a synthetic scenario. Our proposed approach separates a reason to investigate from proof of compromise.

SYNTHETIC EVENT TIMELINE

Illustrative review priorities, not a calibrated risk score. No automated enforcement is performed.

FROM SIGNAL TO RESOLUTION

Awareness becomes action.
Evidence closes the loop.

Explore four fictional security incidents, their risks, and the people responsible for investigation and recovery. This interactive walkthrough illustrates the intended workflow; notification delivery is represented as a preview.

SIMULATED WORKFLOW
ARCVEYL / RESPONSE SIGNAL01 / 06
OBSERVENOTIFYVERIFYCONTEXT
SIGNAL OBSERVED

The right information

Which charger changed, what changed, when it happened, where the evidence came from, and what remains unknown.

The right person

An accountable owner receives a concise notification and opens the investigation. Acknowledgment and escalation are distinct steps.

A defensible outcome

Document the decision and verify the resulting state. Closing an alert should never substitute for confirming what happened.

Operational roles shown are proposed responsibilities, not legal liability or contractual assignments. The customer’s agreements and response plan govern actual ownership. All devices, tickets and events shown are fictional. No real notification is sent and no charger is controlled. Human authorization, telemetry quality and supported integrations determine what can actually be resolved.

ONE ESTATE / FOUR PERSPECTIVES

Zoom out for context.
Zoom in for answers.

Move from the organization to the charger without losing the operational picture.

01 / ◈ ORGANIZATION

Your entire estate.

Understand the inventory across operating groups. Establish the scope of an investigation and identify which teams need to participate.

02 / ▦ FLEET

A shared operating purpose.

Group public, workplace or destination charging. Compare the asset inventory within each fleet before reviewing its evidence.

03 / ⌖ SITE

The local dependencies.

Bring the charging location into focus: network access, power, routing, CMS connectivity and the people who can verify a change.

04 / ϟ CHARGER

The device behind the signal.

Open the station dossier, confirm its CMS and manufacturer, and move into OCPP analysis or connection comparison.

Explore with confidence

Hierarchy navigation is available in the pre-release app. Local inventory is distinct from live telemetry. Demo portfolios are explicitly labeled; unknown coverage is never shown as healthy.

THE ARCVEYL WORKSPACE

Make the evidence useful.

Software your team operates. Built for MSPs, site hosts, CPOs, CMS providers, manufacturers and technical support—not an outsourced monitoring service.

01 / INVESTIGATE

Start with the evidence.

Import normalized OCPP logs and session snapshots. Compare SIM, SSID/BSSID, firmware, backend and route observations. Record responsibility and verification.

Offline tool available
02 / DIAGNOSE

Test the connection.

Prepare Linux DNS, trace, TCP and TLS commands. Review normalized firewall events and preserve diagnostic notes. Commands run on your authorized gateway.

Command builder available
03 / MONITOR

Keep the context.

Compare supplied session observations against earlier evidence. Investigate unexpected changes with clear context; continuous collection requires a connected collector.

Collector integration required
Today’s boundary

The trial supports offline imports and deterministic checks. Continuous collection, production subscriptions, push notifications and active protection are not yet available. Compatibility must be validated per device, firmware and platform.

FIND YOUR WORKFLOW

One evidence layer.
Three ways to work.

Choose the scope that fits your team—from a single investigation to an entire charging estate.

Pre-release edition positioning. Final licensing, pricing and feature allocation are not yet committed. The downloadable app is a single evaluation build.

ArcVeyl FREE: Individual investigation workflow illustrationFREE

Make a supplied log actionable.

Import evidence, compare observations and prepare a useful handoff.

Available investigation foundationExplore FREE capabilities →
ArcVeyl PRO: Deeper operational context workflow illustrationPRO

Follow the change across sessions.

Build on manual investigation with an automation workflow for recurring checks and contextual alerts.

Automation capability previewExplore PRO capabilities →
ArcVeyl TEAMS / MSP: A coordinated estate workflow illustrationTEAMS / MSP

Move from portfolio to device.

Organize chargers by customer, fleet and site, with a shared-workspace model for operational teams.

Collaboration capability previewExplore TEAMS / MSP capabilities →

CAPABILITIES & FEATURES

Know what each workflow gives you.

FREE / INVESTIGATE

From raw evidence to a defensible finding.

Compare this edition ↓
  • Import normalized OCPP JSON or NDJSON and run deterministic evidence checks.
  • Compare supplied connection snapshots, including SIM, BSSID, backend and firmware observations.
  • Prepare DNS, route, TCP and TLS commands for execution by your authorized technician.
  • Review normalized firewall events and export findings for a support handoff.

Available in the evaluation build. Commands are generated, not executed remotely. No live charger enrollment.

PRO / INVESTIGATE + MONITOR

Keep the change in context.

Compare this edition ↓
  • Use the current diagnostic toolkit and manual snapshot comparison.
  • Evaluate the workflow for recurring collection, retained baselines and scheduled diagnostics.
  • Preview contextual alerts that combine identity, connection and configuration evidence.
  • Define verification steps before treating an incident as resolved.

Manual investigation works today. Automated collection, scheduling, persistent history and notification delivery require the production backend and supported integrations; they are not active in this build.

TEAMS / MSP / COORDINATE

Bring the estate and its owners together.

Compare this edition ↓
  • Navigate organization, fleet, site and charger inventory with drill-down views.
  • Record a charger’s CMS and manufacturer to support the investigation handoff.
  • Explore the workflow for shared investigations, assignments and escalation.
  • Evaluate requirements for role-based access, customer isolation and integration APIs.

Local hierarchy navigation is available. Multi-user collaboration, enforced tenant isolation, permissions and APIs are not active in this build. Organization filters are not security boundaries.

SIDE BY SIDE

Compare capabilities. Understand coverage.

Included = proposed edition inclusion of a working evaluation feature. Preview = intended edition capability, not operational. — = outside the proposed edition.

ArcVeyl pre-release edition comparison · availability applies to the current downloadable build
CapabilityFreeProTeams / MSPCurrent availability
Normalized OCPP log analysisIncludedIncludedIncludedAvailable · manual import
Connection snapshot comparisonIncludedIncludedIncludedAvailable · supplied observations
Diagnostic command builderIncludedIncludedIncludedAvailable · technician executes
Normalized firewall log reviewIncludedIncludedIncludedAvailable · supplied logs
Evidence report exportsIncludedIncludedIncludedAvailable · local export
Organization / fleet / site / charger viewsIncludedIncludedIncludedAvailable · local inventory
Continuous telemetry collection—PreviewPreviewNot active · collector required
Scheduled diagnostics & retained history—PreviewPreviewNot active · backend required
Mobile push / email alert delivery—PreviewPreviewNot active · delivery integration required
Shared investigations & team roles——PreviewNot active · identity/backend required
Enforced customer isolation & APIs——PreviewNot active · backend validation required
Automatic blocking or malware removal———Not offered in this release

No managed response service is included. Device and CMS compatibility depends on accessible evidence and validated integrations. Serious findings are not hidden behind an edition upgrade.

Back to editions ↑

RESEARCH

Evidence before reassurance.

Published standards, scoped testing, and clear limitations will guide the work. Findings will distinguish documented research from tests actually performed by ArcVeyl.

⊞

CMS research · Coming soon

No platform catalog or research papers are published in this website build.

Awaiting publication
How will testing claims be presented?

Any future test result should identify the tested model, firmware, platform, date, scope, method and limitations. A proposed test or pilot application is not certification, a security guarantee, or evidence of a vulnerability.

BUILD WITH US

Real environments.
Carefully scoped learning.

↗

MSPs, operators & site hosts

For MSPs, CPOs, fleets, property owners and support teams evaluating the tool in their own environments.

  • Map the available telemetry
  • Review expected operational changes
  • Shape useful alerts and reporting
◈

Manufacturers & platforms

For device makers, CMS providers and open-source maintainers interested in an authorized validation program.

  • Agree device and firmware scope
  • Define safe test conditions
  • Review findings before disclosure

Participation is subject to review and mutual agreement. An inquiry does not authorize testing.

CLEAR ANSWERS

Security without the overclaim.

Is ArcVeyl an antivirus for chargers?

That is a useful aspiration for a simple customer experience. The current trial is an evidence-analysis tool; it does not scan charger operating systems, remove malware, or block attacks.

Can it identify a man-in-the-middle attack?

Backend, certificate and connection changes can be investigation signals when the relevant telemetry is available. They are not conclusive proof of interception. Validating identity and transport requires trusted observations and protocol-specific testing.

Will it know which router or access point a charger uses?

Only when authorized charger, modem, router or Wi-Fi controller telemetry supplies that identity. A public IP or SSID alone does not reliably identify the equipment.

Is this software or a managed service?

ArcVeyl is a software product your team operates to investigate or monitor charging infrastructure. We are exploring free investigation and paid automation/team editions. Pricing and licensing are not finalized. No managed monitoring or incident-response service is included.

PILOT PROGRAM / INQUIRY PREVIEW

Start a conversation

This downloadable build prepares a request on your device. It does not send or store it on a server.