RowDeck: MySQL® Monitor for iPhone
Paged at night with the laptop at home? RowDeck opens on Health, finds the transaction that holds the lock and counts the sessions stuck behind it. Kill the right thread from your iPhone, then do the real fix at your desk.
The built-in demo replays a common MySQL incident. A forgotten transaction holds a row lock on shop.orders, a migration waits behind it, and eight sessions queue up. Pick a step to see its screen.
Try it without a server: on the Connections screen, tap Explore demo data. You need no account, and Pro actions run on the sample data.
InnoDB lock waits grouped under the thread that holds them, with the SQL each one runs and how long it has waited.
The ALTER TABLE queue: who waits for a table metadata lock, which transaction keeps it, and a button to kill the waiting ALTER instead.
The latest deadlock from InnoDB: who waited for what, and which transaction it rolled back.
No KILL rights on Amazon RDS or Aurora? RowDeck calls mysql.rds_kill and names the path in the confirmation.
AUTO_INCREMENT before INSERTs start failing.Purge & Bloat shows how much of each auto-increment range you have used, how far purge has fallen behind, and which tables and indexes hold space for nothing.
INT range of order_items.id, RowDeck warns that every INSERT fails at the end and copies the ALTER that widens the column. ANALYZE TABLE from the list, or OPTIMIZE TABLE after you type the table name. DROP INDEX and ALTER statements go to your clipboard, and you decide when to run them. PRO 
Health up front and a native screen behind each tile, so you skip the mysql prompt on a phone keyboard. The SQL console covers the rest and checks each statement before it runs.
One verdict and ten tiles with thresholds: connections against max_connections, blocked threads, the longest query, queries per second, buffer pool hits, purge lag, auto-increment headroom, deadlocks, replication and disk. It refreshes every 10 seconds while you look at it, in dark or light like iOS.
Every thread from the processlist, waiting ones first. Filter by running, in transaction, over 10 s or waiting, or group the threads by client.
Seen from the replica: IO and SQL threads, lag and the error that stopped a channel. On the source: connected replicas and the space binlogs hold.
Statement digests from performance_schema, sorted by total time, average time, calls or rows examined.
The biggest schemas, tables and indexes, split into data, index and free space.
Browse tables, filter on the server, follow foreign keys, export a page as CSV or copy it as JSON. Row edits come with Pro.
The classifier labels each statement as you type: Read, Write, DDL or Destructive. Free runs reads; Pro runs the rest.
Explains an incident or a lock chain and drafts the fix. It reads a redacted snapshot, shows you what it will send, and runs nothing itself. Free on the demo.
RowDeck asks them in order. A no at any step stops the action, and nothing reaches MySQL.
Free never writes to your server.
Mark a connection read-only and writes stop there, Pro included, until you unlock them for the session.
It runs on every statement, on Free and on Pro.
A preview with the target, schema, connection and PROD badge. Destructive steps, and kills on a Production connection, wait until you type the target.
SELECT * FROM orders WHERE id = 4820118; Read UPDATE orders SET status = 'shipped' WHERE id = 4820118; Write CREATE INDEX idx_orders_total ON orders (total); DDL TRUNCATE TABLE shop.sessions; Destructive SSH with a password, a one-time code or a key: Ed25519, ECDSA or RSA in OpenSSH, PEM, PKCS#8 or PuTTY format, or a Secure Enclave key. Up to two jump hosts behind the bastion.
RowDeck shows the SHA-256 fingerprint of the server certificate on first connect and stops if it changes later.
Passwords, keys and fingerprints live in the iOS Keychain on this iPhone. Face ID opens the app.
Without it, MySQL shows you only your own threads. RowDeck says so and hands you the fix:
GRANT PROCESS ON *.* TO 'oncall'@'%';
RowDeck 1.0 on the built-in demo data.
Health The incident before you open a laptop.
Locks Row locks and metadata locks in one tree.
Kill connection See what it unblocks before you confirm.
Activity Waiting threads first.
Indexes Unused and duplicate indexes, with DROP INDEX copied for you.
Replication Channel status and transactions left to apply.
Slow queries Sorted by total time.
Storage The biggest tables and indexes.
Data Filter on the page or on the server.
SQL console Each statement classified.
DDL What the classifier saw before the statement runs.
Assistant Your model. Every action is your call.
SSH tunnel Your key and your jump hosts.
Point RowDeck at your production server and use every monitoring screen for free. Pay $14.99 once, on the night you need to act.
forever
$0
See everything on one server.
one-time purchase
$14.99
Act on any server.
ANALYZE TABLE and OPTIMIZE TABLE No subscription and no account. The demo lets you try every Pro action on sample data before you buy. Restore Purchases sits on the paywall and in Settings. Outside the US, the App Store shows the price in your currency.
RowDeck works with MySQL 8.0 or newer and MariaDB 10.5 or newer that your iPhone can reach, self-hosted or managed, including Amazon RDS and Aurora MySQL. Percona Server for MySQL works too.
On Amazon RDS and Aurora, where an admin can't KILL other users' threads, RowDeck calls the provider's procedure, mysql.rds_kill. Behind a proxy it sends no KILL, because the thread ID may belong to another server, and gives you the statement to run on the server itself.
MySQL 5.7 and MariaDB before 10.5 are outside the supported range, and TiDB keeps different monitoring tables. The app tells you so when you connect.
Yes. Turn on the SSH tunnel in the connection and sign in to the bastion with a password, a key or a Secure Enclave key made on this iPhone. Keys can be Ed25519, ECDSA or RSA in OpenSSH, PEM, PKCS#8 or PuTTY format, with or without a passphrase. One-time codes work when the server asks for them.
If the bastion sits behind another host, add up to two jump hosts. RowDeck pins each host key on first connect and refuses to go on if one changes.
RowDeck connects straight to your server or through your bastion. No RowDeck server sits in between, and you need no account. Passwords and keys stay in the iOS Keychain.
Crash reports go to Sentry and usage counts to our own analytics server once you tap Done on the first screen, where both switches start on. You can turn either off there or later in Settings › Privacy. Neither contains your SQL, schema, table or column names, hostnames, values or credentials. The details are in the privacy policy.
No. The monitoring screens need read-only grants, and the connection form lists them for MySQL and for MariaDB. The one that matters most is PROCESS: without it MySQL shows you only your own threads, and RowDeck says so on each screen instead of showing an empty list.
Pro actions need CONNECTION_ADMIN to kill other users' threads; on Amazon RDS and Aurora, RowDeck uses the provider's kill procedure instead. A metric the server hides shows a reason, never a zero.
KILL QUERY stops the running statement and keeps the connection and its transaction. KILL CONNECTION closes the connection and rolls back its open transaction.
A thread asleep in an open transaction runs no statement, so KILL QUERY changes nothing and its locks stay. RowDeck reads what the root is doing and offers the kill that frees the queue.
Free never writes: console reads run inside a read-only transaction. With Pro, every write passes four checks in order: Pro, the connection's Read-only switch, the classifier and your confirmation. Destructive statements wait until you type the target, and a connection marked Production gets a PROD badge and stricter confirmations.
RowDeck copies DROP INDEX and ALTER … BIGINT for you and leaves running them to you. It doesn't purge binlogs or skip a transaction on a replica, and it never asks the server for LOAD DATA LOCAL or for several statements in one call.
You can. At 3 a.m. on a phone keyboard, RowDeck saves you the joins across performance_schema and information_schema: the lock tree, the waiting ALTER and the transaction behind it are one tap from Health.
A redacted snapshot of the screen you asked about. Host, port, IP addresses, connection names and passwords never leave, and values inside statements never leave either. For cloud models, schema, table and column names go out as placeholders like table_1, and RowDeck puts the real names back on your iPhone.
Requests go from your iPhone to the provider you chose with your own key (Anthropic, OpenAI, OpenRouter, Z.ai or any OpenAI-compatible endpoint) or to your own Ollama. You see what the model will get before you send. The assistant is part of Pro, free on the demo, and leaves running SQL to you.
No. Pro is a single purchase of $14.99 tied to your Apple Account. Monitoring stays free, with no account and no trial clock.
No. RowDeck does no background work and doesn't watch servers while it is closed. Keep your alerting where it is: RowDeck is the screen you open after the page.
We built RowDeck for iPhone, in portrait. It has no iPad layout of its own.
Amazon Web Services, AWS, Amazon RDS and Amazon Aurora are trademarks of Amazon.com, Inc. or its affiliates. RowDeck is not affiliated with or endorsed by Amazon.
The problems that page you at night, one page each: the SQL to run by hand and what RowDeck shows.
Add a server, pin its certificate and keep every monitoring screen free. Pro unlocks the actions for the night you need them.