Keepers that run your on-chain operations. So you don’t have to.
We build and operate automation keepers for EVM: portfolio rebalancing, order matching, liquidations, and scheduled execution. Backed by quant research and pre-trade risk scanning, so every action is tested before it’s live.

Keeper types
Rebalance, Matching, Liquidation, Jobs
Onboarding a limited number of teams
Supported chain list coming soon
Runs before every keeper deployment
Public status page in progress
Built for Serious Traders & Protocols
Eliminate operational overhead with autonomous, institutional-grade on-chain execution.
For Traders
Stop watching the chart at 3 AM. Set your rules once: rebalance bands, limit/TWAP orders, take-profit and stop conditions. Our keepers execute on-chain, 24/7, with gas and slippage controls.
- Custom rebalance bands & target asset weights
- On-chain limit, TWAP & multi-stage stop orders
- Dynamic max gas price & strict slippage protection
For Small Protocols
You don’t need to hire a DevOps team to run keepers. We operate order matching, rebalancing, liquidations and epoch/cron jobs for your contracts, with monitoring, alerting and failover included.
- DEX order matching & batch settlement execution
- Continuous liquidation monitoring to limit bad debt
- Epoch updates, yield harvest & automated oracle pokes
What our keepers do
Four kinds of on-chain automation for EVM, built, tested and operated by us.
Rebalance
Keeps a portfolio or LP position at your target weights or inside a price band. Adjusts automatically when it drifts past your threshold, with gas and slippage limits.
Order Matching
Matches limit, stop and TWAP orders for a DEX or order-book contract. Processing order is transparent, with logs you can reconcile.
Liquidation
Watches health factors and executes liquidations at the right time, helping the protocol limit bad debt.
Scheduled Jobs
Harvest, compound, epoch updates, oracle pokes and other recurring on-chain tasks.
Why you can trust it
Three layers of protection around every keeper: test first, scan the target, monitor continuously.
Tested before live.
Every strategy is backtested and fork-simulated before it runs on mainnet.
Transactions are dry-run against a fork of the latest chain state to check gas, slippage and execution logic, so reverts are caught before real funds move.
Risk-scanned.
Target contracts are scanned for financial logic and admin permissions before a keeper interacts with them.
The risk scanner reviews ownership, upgradeability, admin-controlled functions and pool or oracle conditions, and the keeper is limited to the calls you approve.
Monitored 24/7.
Alerts go to Telegram or Discord. A circuit breaker halts the keeper on abnormal price, gas or revert behavior.
If prices move abnormally, gas spikes, or the revert rate climbs, the keeper pauses itself and notifies you instead of continuing blindly.
From your rules to a live keeper
Four steps, from first conversation to ongoing operation.
Tell us your rules
Strategy and trigger conditions
Define what should happen and when: rebalance thresholds, order-matching logic, liquidation targets or a recurring schedule.
We scan & simulate
Risk scan, backtest, fork test
We scan the target contracts, backtest your rules and dry-run transactions on a chain fork, including gas and slippage under different conditions.
Deploy keeper
Non-custodial, minimal permissions
We deploy the keeper with permissions limited to the functions you approve, and set up your gas, slippage and circuit-breaker limits.
Monitor & report
Dashboard, logs, periodic reports
We watch the keeper around the clock, send alerts when something is off, and share logs and periodic reports so you can verify every action.
Non-custodial by design.
The keeper can only call the functions you allow. It does not hold keys that can withdraw your funds.
Strategies your keeper can run
Start from a proven template instead of writing automation from scratch. You choose the parameters and limits; the keeper executes them on-chain and enforces your guardrails.
Rebalance Band
Keeps a portfolio or LP position near your target weights. The keeper only acts when an asset drifts outside the band, so you avoid needless trades and gas.
Best for: Index-style portfolios, treasury allocations, LP position management
You configure
- •Target weights per asset
- •Band width (absolute or relative)
- •Minimum trade size
- •Cooldown between rebalances
Keeper enforces
- •Max gas price
- •Max slippage per swap
- •Price-deviation check against an oracle
- •Pause on repeated reverts
strategy: rebalance_band
assets:
ETH: { target: 50% }
USDC: { target: 50% }
band: 5% # act only outside +/- 5%
cooldown: 6h
limits:
max_gas_gwei: <your cap>
max_slippage: <your cap>Research that validates every keeper
We use quantitative research to test strategies before they go live, not to promise returns. Each keeper goes through the same validation pipeline.
Historical backtesting
Every strategy rule is replayed on historical on-chain and market data, including fees, gas and slippage, before we consider deploying it.
Fork simulation
Keeper transactions are dry-run against a forked copy of the target chain so reverts, approvals and edge cases show up before real funds are involved.
Parameter stress tests
Band widths, intervals and limits are tested across volatile and illiquid conditions, so you know how the keeper behaves in bad weather, not only in calm markets.
Contract & risk review
Before a keeper touches a contract, we review its financial logic and admin permissions and set minimal-permission rules for what the keeper may call.
Published research and backtest reports
We will publish methodology notes and validation reports for each strategy template.
Need a keeper for your strategy or protocol?
Tell us what you want automated. We’ll reply within 48 hours with a scoped plan.