One workspace to build, audit, and prove
Developers write and store contract source in the Contract IDE. Auditors work the same code in the Auditing IDE. Both run against the same isolated fork of real chain state, in the browser.
Three workbench surfaces on one shared foundation
The Contract IDE, the Architecture Explorer and the Auditing IDE are the three surfaces you work in. Underneath them sits one shared foundation: the fork environments the work runs on, and the analysis engine that reads the bytecode. Beside them sits the intelligence layer, which answers questions about contracts rather than being a place you take one apart: Tradar, contract search over indexed Ethereum bytecode, available today; and Janus AI, held to the same proof bar, in development and not available yet, listed here as unfinished rather than left out.
Contract IDE
Write, compile, and deploy Solidity and Vyper in the browser, and open Rust programs for analysis. Source and development notes stay in private workspace storage.
- InputSolidity, Vyper; Rust read-only
- Runs ona pinned fork (EVM) or captured account state (Solana)
- Handoffread-only, revocable
Architecture Explorer
A durable map of actors, controllers, and upgrade authority, resolved from on-chain state. The explorable graph is an EVM capability.
- Readsstorage slots on a pinned fork
- Resolvesactors, controllers, upgrade authority
- Outputa revisioned map
Auditing IDE
Every panel a security engineer expects, rebuilt for the EVM — plus Solana program scanning and tracing, against live state you control.
- Works onEVM transactions, calldata, storage; Solana programs and accounts
- PanelsComposer, Scanner, MorphVM, and six more
- Outputa finding, replayed on the pinned fork or the captured account set
Fork environments
Isolated forks of live chain state, pinned to a block. Impersonate any sender and override balances.
- ScopeSix EVM L1s and L2s, plus Solana
- Pinned toa block you choose (EVM networks)
- Keysnone; senders are impersonated
Analysis engine
Control-flow, storage-flow, and value-flow recovered from raw bytecode, then proved by replay.
- InputEVM bytecode; Solana program source
- Sourceoptional on EVM; the substrate on Solana
- Outputa runnable proof-of-concept
Tradar
Contract search over indexed Ethereum bytecode — opcodes, selectors, proxy and admin shape. Available today.
- Indexed200,000 Ethereum deployments
- Groups51,338 code families
- Coveragea slice — reported on every response
Janus AI
An agentic auditor that works the same fork and must replay a claim before it reports one. In development.
- Works ona pinned fork, deployed bytecode
- Gateno replay, no finding
- Statusin development — not yet available
What is available on each ecosystem
Contracts on Ethereum and the networks like it run in the EVM, the Ethereum Virtual Machine. Solana programs run in the SVM, the Solana Virtual Machine. Both are generally available here. Some capabilities exist on one and not the other, because the two runtimes do not model the same things: the EVM has contracts, storage slots and calldata; Solana has programs, accounts and instructions. This table is what the platform serves today — not a roadmap. Last verified 10 September 2026.
| Capability | EVM 6 networks | Solana SVM |
|---|---|---|
| Environment creation and state restoration EVM sessions pin to a historical block. Solana sessions capture live account state as your program touches it, because what we read is the cluster's current account state rather than an archived slot. | Available | Available |
| Source compilation and deployment Solidity and Vyper compile and deploy in the browser. Rust is read and analyzed as source; there is no Anchor toolchain, so nothing is compiled. | Available | Not available |
| Transaction and instruction composition Solana sessions can be funded and read. Building an instruction by hand is an EVM-side capability today. | Available | Not available |
| Execution tracing and state inspection Compute units, logs and account diffs on Solana; call traces, storage writes and gas on EVM. | Available | Available |
| Scanning Twenty Solana program detectors, checked against a public corpus of known bugs. | Available | Available |
| Gas sweeps with a trace Runs from the Composer. Fuzzing is an engine capability that drives concolic execution; there is no fuzzing panel. | Available | Not available |
| Authority mapping The explorable graph is an EVM capability. On Solana the same questions — signer required, PDA ownership, upgrade authority — are answered by the Scanner as graded findings. | Available | Not available |
| Evidence export and replay Solana emits SARIF with a proven-or-refuted verdict; EVM emits a trace and a runnable proof-of-concept. | Available | Available |
A capability marked Not available is one we have not built — it is never a hint at a roadmap. For what an integration would involve, talk to us or read the API reference .
Start on a fork.
Open the workspace in the browser. Nothing to install.