Stop stressing about ABIs, keys, and integration testing.
Say hello to web3’s first secure-by-design dev tools.
Build safer dapps
faster
Focus on dapps, not infrastructure
Spend your time on what and let us handle how.
Manage your team’s web3 development, testing, deployment and upgrade workflows in custom, security-focused CI/CD pipelines.
Cubist takes care of what’s tricky—and risky—from dev credential management to custom rollups to cross-chain bridge code generation.
Secure your dapps
and web3 devops
Our founders include computer security professors from Carnegie Mellon University and UC San Diego and a former Head of Fraud Ops for a high-risk financial product. Everyone on our engineering team has a computer science PhD and security-related industry experience.
We’re experts in
We’re here to help you (safely) build web3’s Next Big Thing.
Do you want to...
The web3 dev tools you’ve been searching for
Pick and choose tools to implement the secure dev workflows that are right for your team.
The first multi-chain and cross-chain SDK
Multi-chain, multi-language development: develop for EVM and non-EVM chains, and write off-chain code in JavaScript, TypeScript, or Rust.
Automatic cross-chain interaction: write code as if everything runs on a single chain; Cubist turns cross-chain calls into secure bridge code using your choice of bridge provider.
Push-button deployment: deploy to many chains with a single click.
Wallet management for your dev team
Separate authentication credentials: defend against app compromises and insider threats by giving access to fine-grained, revocable privileges—not the keys that control all your money.
Proactive monitoring: don’t wait for alerts about suspicious transactions! Approve sensitive operations before they hit the chain.
Interoperability: use Cubist’s credential management standalone or with your existing wallet provider, and seamlessly export logs to your crypto accounting system.
An A+ web3
testing framework
Testnet libraries: instantly spin up private testnets and funded test accounts for many chains. Never wait for a faucet again.
Simulation testing: there are so many good (bad) choices! Simulate terrible latency, time travel to a bad day on mainnet, or run thousands of trials under random conditions.
Automation tools: seamlessly run integration tests on configurable testnets in your CI.
Custom rollups
with familiar tools
High level: write app logic in familiar, easy-to-use, easy-to-test languages.
High performance: get 10-100x lower latency with custom rollups than with general-purpose solutions.
Future proof: target the latest proof systems without re-writing your code.
You’re building a new cross-chain application
Write your cross-chain dapp as if it’s single-chain, and Cubist will generate the secure bridge code that lets your smart contracts interact seamlessly. If you want to change bridge providers (or even chains!), Cubist makes it as easy as changing your config and re-deploying your contracts. Use our cross-chain NFT marketplace as a jumping off point.
You’re designing your dapp’s testing pipeline
Your tests are repeatable—from developer to developer or in CI—until you decide to change something. Forget about manually spinning up test environments: with a few lines of configuration, you can go from a localnet to a private testnet, change chains altogether, or simulate a wide range of mainnet conditions. Get inspired by our customizable integration test examples.
You’re migrating your dapp from one chain to another
Keep your dapp code the same. Let Cubist automatically expose your contracts to a new chain—or change chains, and use Cubist to retain your loyal users on the original chain.Take our upgrade example for a spin.
You’re managing a team of developers
Create user groups with different privileges, and make developers or services only as powerful as they need to be—without giving them access to sensitive keys. Force key rotation, revoke access to privileges, and proactively monitor for usage anomalies that might indicate a security breach. Start from our team management example.
