Security & data handling

Your design stays on your network.

Probe is self-hosted. Design data — ODB++, netlists, BOMs, schematics, datasheets — lives in your own database and your own file volumes. Probe contains no generative AI model and never calls one. The only model it runs is a local embedding model for datasheet search.

Data flow

How your design moves — and where it doesn't go

Design data stays in your environment all the way. The only things that leave your network are what you configure yourself: catalogue lookups, datasheet pages and SSO.

1 · InputECAD exportYou export ODB++ — or schematic and BOM before layout — from your EDA tool.
→
2 · StorageYour databaseProbe loads the design into your own PostgreSQL and your file volumes. Nothing is sent to E#.
→
3 · ReviewYour AI toolThe assistant on the engineer's machine reaches Probe via MCP tool calls under your own vendor agreement.
→
4 · ResultsProbe's browserFindings and citations are shown tied to net and component. Design data never leaves your network.
Where the review runs

Two options — both under your control

On-premises

Recommended for sensitive IP. Docker Compose (Linux or Windows) or Windows-native. A carry-in package supports air-gapped hosts. E-Sharp holds nothing and has no remote access.

Evaluation server

A dedicated server at E-Sharp in Azure (Sweden Central) that starts empty. Access is by personal invitation, and the server and its data are deleted when the evaluation ends.

Your AI tool

The generative assistant (e.g. Claude or Copilot) runs on the engineer's own machine under your own vendor agreement. It reads Probe via tool calls; retention is governed by your agreement with the provider, not by us.

What is stored

Design data with you, no secret phone-home

Design data

ODB++, netlists, BOMs, schematics and datasheets live in your PostgreSQL database and your file volumes. Nothing is sent to E-Sharp.

Personal data

Limited to each signed-in user's identity, display name and email, plus audit records of that person's writes.

No telemetry

Probe has no telemetry or licence phone-home. The licence fingerprint is copied and emailed by a human — it contains host identifiers and pseudonymised activity, but no design data.

Outbound connections are configuration choices — catalogue lookups (DigiKey, LCSC), fetching datasheet pages, SSO and licence/Trace calls. All are off until configured.

Access & SSO

Your identities, your roles

SSO

OpenID Connect with PKCE against your Okta or Microsoft Entra tenant. IDE assistants use personal keys that inherit the owner's current roles.

Roles & audit

Six roles, and authorisation can be phased in (Open, rollout, Enforcing). Audit events are append-only and security events can be forwarded to a SIEM.

E-Sharp's access

On-premises: we reach nothing. Evaluation: the staff running the Azure subscription can reach the server to run and support the evaluation. E-Sharp operates no multi-tenant SaaS.

The reference deployment is a large multinational that has completed a formal Infosec review. Security questions? security@esharp.se.

Operations & installation

You own the operations

Installation

Docker Compose on Linux or Windows, or Windows-native. A carry-in package supports air-gapped hosts with no outbound network. Upgrading is a matter of switching to a new image.

Storage & backup

A PostgreSQL database and your file volumes, in your environment. Backup, replication and retention follow your own routines — nothing sits with E#.

Outbound traffic

All outbound connections — catalogue lookups, datasheet pages, SSO, licence/Trace calls — are off until you configure them. No design data is part of any of them.

Run the review in your own environment.

Book a demo or start a time-limited evaluation. You run the review yourself — we don't review your boards for you.

Book a demo of Probe

Show us your board — we review it and go through the findings together.

Prefer to email? info@esharp.se