Workspaces
Keep your security work connected. Organize projects, contract inventory, team access, review documents, audit scope, findings, and remediation tracking in one workspace instead of scattering them across spreadsheets, chat threads, and static PDFs.
Security context breaks when every review lives in a separate document
Most teams track deployed addresses in one spreadsheet, keep threat models in a doc, receive audit findings as a static PDF, and coordinate fixes in chat. When a contract upgrades or a second review starts, nobody can see which addresses were in scope, which findings were reproduced, or whether a fix was verified.
Register contracts once
Keep a canonical inventory of project contracts keyed by chain and address, linked to the source revisions and deployment context your team actually reviews.
Lock scope and documents
Define audit scope, maintain protocol overviews, threat models, and invariant registries alongside the code, and keep team permissions scoped to the project.
Record findings with evidence
Capture structured findings linked to Contract IDE and Auditing IDE sessions, separating scan leads, reproduced results, and reviewed findings.
Share reports and track fixes
Publish controlled report snapshots with revocable access grants, record tamper-evident audit attestations, and track each finding from open report to verified fix.
What Workspaces manages for your team
Every capability below is available in the web application today.
Projects and contract inventory
Organize work by project and maintain a canonical inventory of contracts keyed by network and address. Attach human-readable labels, deployment metadata, and source references so developers and auditors always look at the same target set.
Team access and permissions
Workspaces are private by default. Invite developers, internal reviewers, or external auditors with role-based project permissions so each participant sees only the projects and engagements they are authorized to access.
Documents and audit notebooks
Maintain workspace documents and per-audit structured notebooks — including protocol overviews, threat models, and invariant registries — right next to the contract inventory and review scope.
Audit scope and findings
Lock the target contracts and source revisions for an audit engagement. Record structured findings with severity, affected contract and function, reproduction steps, and status so findings stay queryable across reviews.
Report sharing and attestations
Publish an audit report snapshot and share it with stakeholders via explicit, revocable access grants. Issue tamper-evident audit attestations tied to the exact scope and findings snapshot.
Remediation tracking
Track every finding through developer response, patch submission, and reviewer verification. Re-open the affected contract in Contract IDE or Auditing IDE to confirm the fix holds.
Inventory & scope
- Project contracts
- Role-based access
- Review notebooks
Findings & review
- Severity & status
- IDE trace links
- Discussion threads
Reports & fixes
- Revocable snapshots
- Audit attestations
- Remediation status
Connected directly to Contract IDE and Auditing IDE across EVM networks and Solana
One record from initial scope to verified fix
Instead of reconciling three versions of a report against a moving repository, the engineering team and the audit team work from the same project record: which contracts are in scope, what each finding affects, and which fixes have been verified.
- Scoped inventory: every finding points to a registered contract address or source revision in the project inventory
- Structured lifecycle: findings move through clear states — open, acknowledged, remediated, and verified — with a recorded history
- Controlled distribution: external stakeholders read a pinned report snapshot through a revocable grant rather than an unversioned attachment
Built for teams that treat security as an ongoing record
Protocol teams
Maintain a living record of your deployed contracts, architecture notes, and review history across upgrades so new engineers and returning auditors start with full context.
Auditors and security researchers
Keep threat models, invariant lists, and findings connected to the contracts under review, then deliver a controlled report snapshot and track client remediation without losing the evidence trail.
Contract developers
Share frozen source and deployment state from Contract IDE into a project workspace, respond to findings directly, and verify fixes against the original reproduction.
What Workspaces covers and where its boundary sits
Workspaces organize project records, scope, documents, findings, and report sharing across reviews.
- Projects and inventoryAvailable across Ethereum, BNB Chain, Polygon, Arbitrum, Optimism, Base, and Solana
- Documents and notebooksAvailable. Workspace documents plus per-audit protocol overview, threat model, and invariant notebooks
- Findings and remediationAvailable. Structured findings, severity and lifecycle tracking, and remediation verification workflow
- Sharing and attestationsAvailable. Role-based workspace access, revocable report grants, and tamper-evident audit attestations
- Execution and compilationCompilation runs in Contract IDE and transaction replay runs in Auditing IDE
- Default privacyAll projects, documents, and findings are private to workspace members unless an explicit report grant is created
Keep your contracts, audits, and fixes in one workspace.
Launch the app to create a project workspace, or book a demo to walk through a full review and remediation workflow with us.