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.
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.
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.
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.
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.
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.