01 / AVAILABILITY
Source is the current native distribution.
The public repository contains the engine, interfaces, models, and tests. A checkout identifies its exact implementation revision; signed packages and supported-platform matrices are not yet published.
Rust source
The public repository provides the engine, CLI, UI, Python bindings, WASM bindings, and test material.
Web lab
The browser route is a constrained, client-side evaluation target rather than a hosted compute service.
Commercial delivery
There are no signed installers, entitlements, billing accounts, hosted projects, or published support terms.
02 / NATIVE BUILD
Build the CLI or egui desktop application.
The CLI accepts decks and writes result files; the desktop package provides the native graphical application. Both build against the checked-out rspice-core revision.
git clone https://github.com/JaimeHW/RSpice.git
cd RSpice
cargo build --release -p rspice-cli
target/release/rspice run example.spcd RSpice
cargo run --release -p rspice-ui03 / BROWSER PREVIEW
Browser path: summaries, DC, AC, and transient.
The experimental lab runs the WebAssembly binding in the browser. It does not create accounts, synchronize projects, allocate managed runners, or expose every native analysis.
- Available: netlist summaries and client-side DC operating-point, AC, and transient result snapshots.
- Not available: parallel campaigns, managed storage, hosted runners, collaboration, or full parity with the native interfaces.
- Data path: the current lab has no account or project-sync service.
04 / COMMERCIAL PATH
Proposed license structure.
The current plan uses paid native editing seats, free view-only review, and separate usage billing for managed runner time and storage. Checkout is not active.
Native license
A commercial seat covers desktop, CLI, Python, and CI use without requiring hosted storage or simulation.
Hosted runner and storage usage
Managed jobs and retained outputs use separate metering so estimated cost can be shown before submission.
05 / ACCOUNT BOUNDARY
Account services will use a separate application service.
Future registration, organization management, billing, project access, collaboration, publishing, and cloud execution belong to the authenticated application. The public site remains account-free.