Automate crypto actions with conversation

Tell Qleva what you want to do. Review the plan in plain English. Approve it once, then let your smart wallet handle the timing.

Launch AppSee how it works
User request
Buy $20 of ETH every Friday.

No bots. No hidden trades.

Qleva turns your intent into a clear execution plan before anything can run.

Scheduled Buy26 runs
PAY WITHUSDC
BUY $20ETH
RunsEvery Friday, 09:00
First runFri 28 Aug
Runs until26 Feb 2027

Enforced on-chain. Qleva cannot exceed these, even by mistake.

Can only swap the tokens shown above
Proceeds return to your wallet only
Expires automatically when the schedule ends
  • Base logo
  • Privy logo
  • Alchemy logo
How it works

From request to execution in three clear steps

Qleva keeps the process simple enough to trust and detailed enough to verify.

01

Describe

Say the action the way you would say it to a person.

Buy $20 of ETH every Friday morning.
02

Review

Qleva converts your request into a structured plan with asset, amount, timing, wallet, gas estimate, and limits.

Recurring buy Pay with: USDC Buy: $20 of ETH Runs: Every Friday, 09:00
03

Approve

Activate only when the plan looks right. Pause, edit, or cancel whenever needed.

Approval required Max gas: $4.00 Status: Ready
Start with a request

Automations for the crypto actions you already repeat

Recurring buys, scheduled payments, price triggers, and multi-step strategies where the exit measures from what the entry actually paid.

Launch App

One sentence in. One card to check.

Scheduled Buy26 runs
PAY WITHUSDC
BUY $20ETH
RunsEvery Friday, 09:00
First runFri 28 Aug
Runs until26 Feb 2027

Enforced on-chain. Qleva cannot exceed these, even by mistake.

Can only swap the tokens shown above
Proceeds return to your wallet only
Expires automatically when the schedule ends
Security

Assume we get hacked

Most products ask you to trust that they will not misuse access. Qleva is built so the question does not arise: the limits you approve are enforced by the contract holding your funds, not by our servers. So the useful test is the hostile one.

Enforced by:the smart contract holding your funds
Not enforced by:Qleva's servers, or a promise from us
Read the security model

If our servers were fully compromised

Cannot move your funds to another address

The recipient is written into the permission and checked on every run.

Cannot swap for a token you did not choose

Both sides of the pair are fixed at signing. Neither can be substituted.

Cannot spend more than you approved

Capped per run, and again by the number of runs. Approvals do not stack.

Cannot keep going indefinitely

Every permission carries an expiry. It stops on its own with nobody watching.

Could run your automation at a worse moment

Within the cap you already approved. This is the risk that remains, and we would rather write it down than let you find it.

And a week later, you can still see every one

Signing is not the end of it. Each automation stays on one page in plain English — what it does, when it next runs, how many runs are left, and a pause that takes effect before the next one.

4 automations2 active

ListGrid

Buy $20 of ETH every Friday

Next Fri 28 Aug · 5 of 26 done

Active

Buy ETH on a 5% dip, take profit at +10%

Waiting on ETH −5% from $2,410 · step 1 of 2

Active

Send 100 USDC to Maya on the 1st

Next 1 Sep · 3 of 12 done

Paused

Take profit when ETH rises 20%

Filled 12 Aug at $2,892

Done
Pausing stops the next run immediately. And nothing can outlive what you signed: every permission carries a run count and an expiry the contract enforces, so it ends on its own even if nobody is watching it.

Priced against the wallet you actually hold

Qleva reads your balances straight from Base and prices them from the same oracle the engine trades on. So the figure on this screen and the figure a condition is checked against are the same number — not two opinions that happen to agree.

Wallet value

$6,942.30

Base

ETH

Ethereum

$4,102.30

1.4210 · 59%

USDC

USD Coin

$2,840.00

2,840.00 · 41%

A token with no market shows its balance and no price, rather than a guess.

Everything needed to automate safely

Qleva keeps powerful actions understandable, reviewable, and easy to manage.

Natural-language requests

Describe the outcome without learning another DeFi interface.

Structured execution plans

Review action, asset, amount, timing, wallet, gas, and limits.

Simulation-first flow

See expected behavior before approval.

Recurring schedules

Run buys, transfers, and payments on a predictable cadence.

Conditional triggers

Create rules based on price movement or portfolio thresholds.

Spending limits

Control how much an automation can move.

Smart-wallet execution

Use wallet permissions built for safer automation.

Automation history

Track every scheduled, completed, paused, and failed action.

Pause and cancel

Stop an automation at any time — and every permission expires on its own.

Launch App

Not a bot. Not another dashboard.

Qleva gives you automation without hiding the details or forcing you through manual DeFi steps every time.

Dashboards

Setup styleTune controls
TransparencyVisible but complex
Approval controlManual controls
Recurring actionsConfiguration-heavy
User effortHigh setup cost

Trading bots

Setup styleConfigure strategies
TransparencyOften opaque
Approval controlVaries by bot
Recurring actionsStrategy-focused
User effortHard to audit

Qleva

Recommended
Setup styleDescribe the outcome
TransparencyReadable plan first
Approval controlHuman approval gates
Recurring actionsBuilt for routines
User effortLow, with clear limits

Questions worth asking before automating crypto

Qleva is built for users who want convenience without losing control.

No. Qleva is non-custodial — your funds stay in your own smart wallet at all times. What you grant is a scoped, revocable permission called a delegation, which lets Qleva execute one specific kind of action within limits you set. Qleva never takes possession of your assets.
The blockchain does. Every automation carries caveats — a maximum spend per run, a maximum number of runs, the exact token pair, the recipient and an expiry. These are checked by the smart contract when the transaction is submitted, so exceeding them fails on-chain. It is not a limit checked in our own code and promised to you.
A smart wallet is a wallet controlled by a smart contract rather than a single private key, which lets it hold programmable permissions. That is what makes safe automation possible: a normal wallet can only sign one transaction at a time, so automating it would mean handing over your key. A smart wallet can instead grant a narrow, revocable permission with spending limits built in.
Base, Coinbase's Ethereum layer-2 network. Base was chosen because fees are low enough that a weekly automation is not eaten by gas, and because it has the liquidity depth that price triggers need to execute at a sensible price.
Yes, at any time. Pausing stops execution immediately. Revoking removes the underlying permission entirely and is an on-chain action, so it does not depend on Qleva processing your request.
Qleva compiles your request into a structured plan and shows it as a card: the exact amount, the exact trigger, the number of runs, the expiry and the permission it needs. Nothing exists on-chain until you approve that card, and what executes is exactly what it described.
Qleva does. Scheduled and price-triggered executions are submitted by Qleva's operator wallet, so you are only charged the amount the automation is for. Instant swaps you make yourself are paid from your own wallet, with a measured estimate shown before you sign.
Recurring buys on a schedule (automated DCA), price-triggered orders, recurring payments to an address, and multi-step strategies where a second action is measured from the price the first actually filled at — including take-profit and stop-loss as a single exit, and trailing stops.
No. You describe what you want in ordinary language and read a plain-English card before anything happens. Terms like slippage and gas are explained where they appear rather than assumed. If you can describe the outcome, Qleva handles the mechanics.
The activity view shows the failed attempt with the automation, the time and the reason. Failures are classified: a temporary problem such as a busy network is retried, while a configuration fault pauses the automation immediately rather than retrying something that cannot succeed.
Read docs

Crypto automation that feels human

Describe what you want. Review what will happen. Approve only when it makes sense.

Send USDC every month.

Recurring payment ready for review. Approval required.

Launch AppView Docs

Qleva gives you a simpler way to handle recurring crypto actions without surrendering control to a black box.