ProbeDeck Downloads & RevenueProbeDeck: ClickHouse® Client · App Store
Not in any tracked top chart right now.
Updated 5 Nov 2026 · rankings refresh through the day
DeveloperVladimir Chemeris
CategoryDeveloper Tools
PriceFree
Released
Rating★ 0.0 (0)
Version1.2.7
Age rating4+
First seen by us
7 Oct 2026
ProbeDeck: ClickHouse® Client update history & changes
Last change · 5 events since 27 Jul 2026Full timeline ↓📦Updated to version 1.2.7🆕First spotted by AppInsider📈Dropped out of every chart we track📦Version 1.2.6🆕Released on the App Store
Full timeline · 5 events
- 📦ProbeDeck: ClickHouse® Client updated to version 1.2.7Test Connection gives up after 10 seconds when the server stays silent and counts the seconds while it waits. In 1.2.6 it could hang for a minute. The dashboard reports a silent server in about 5 seconds, down from several minutes.
After a failed test, the form shows what to check: the port, firewall or VPN if the server never accepted the connection, or a busy server if it connected and sent no reply. Error messages appear in all 11 app languages.
For a ClickHouse Cloud address, the form suggests port 8443 with TLS and sets both in one tap. Paste a full https:// URL into the host field and the app fills in the host, port and TLS. Enter a native protocol port such as 9000 or 9440 and the form offers the matching HTTP port.
In the free version, + opens the ProbeDeck Pro screen once you have a saved connection. That screen has a new Edit Current Connection button, so you can open the saved connection and fix it. If the app cannot reach your server or sign in, the error screen shows Edit Connection next to Retry, and the connection menu has the same item.
If you swipe down a form with unsaved changes, the app asks before it discards them.
Error reports from failed connections include the port, whether you use TLS or SSH, and the kind of address, such as ClickHouse Cloud or a private IP. They never include the name or IP address of your server or SSH bastion. You can turn them off in Settings under Privacy.… more - 🆕ProbeDeck: ClickHouse® Client first spotted by AppInsider#43 in Top Free · Developer Tools · United Kingdom
- 📈ProbeDeck: ClickHouse® Client dropped out of every chart we trackLast seen 6 Oct
- 📦ProbeDeck: ClickHouse® Client version 1.2.6On a slow connection, the dashboard and Storage show placeholders while data loads. The status line reads Loading…, and after 3 seconds it shows how long the app has waited for the server. Before this update it read Unknown until the first answer arrived.
Refresh keeps the current values on screen and marks them as updating. Auto-refresh waits for the running request instead of starting a new one every 5 seconds.
Allow local network access in Settings, come back, and the app repeats what failed: Test Connection in the connection form, the monitoring screen, or your last AI question. If you switched AI providers in the meantime, the app does not resend the question.… more - 🆕ProbeDeck: ClickHouse® Client released on the App Store
Collected from the stores by AppInsider since we first spotted the app. Dates are when we saw each change.
Rating
0.0 ★
0 ratings
Measured
ProbeDeck: ClickHouse® Client on the App Store
App details
App ID
6791261174
Publisher
Vladimir Chemeris
On the store since
Jul 2026
Under a year
Minimum OS
iOS 17.0+
iPhone XS and later
Devices
iPhone · iPad
Universal purchase
Content rating
4+
Languages
11
EN FR DE IT JA KO PT RU ZH ES ZH
Size
21 MB
Also listed in
Utilities
Where it ranks now
Every top chart it appears in across 30 countries.
| Country | Charts | Rank |
|---|---|---|
| Not charting right now. | ||
Ratings
App Store, worldwide.
Rating
0.0 ★
0 ratings
Measured
Ratings
0
Measured
About ProbeDeck: ClickHouse® Client
ProbeDeck is a secure mobile client compatible with ClickHouse® servers, built for cluster operations from your iPhone.
ProbeDeck is built for DevOps, SRE, platform and data engineers on call. Connect over TLS, through an SSH tunnel or a bastion. See cluster health, find the query that is eating the cluster and kill it in seconds, while production credentials never touch someone else's server.
WHY PROBEDECK
• Trust-first. Your credentials stay on your device and never leave it. There is no backend, no proxy, no traffic relay. Your connection goes straight from your phone to your server.
• It knows ClickHouse. Replication lag, read-only replicas and Keeper trouble, parts and merges, "too many parts", stuck mutations, disk pressure. These are the pages you get, so this is the first screen you see.
• Safety on each statement. ProbeDeck classifies your SQL before it sends anything. DROP, TRUNCATE, ALTER UPDATE and ALTER DELETE, DETACH, DROP PARTITION, OPTIMIZE FINAL and KILL need a type-to-confirm step showing the exact target. Costly statements carry a warning. Set a connection read-only and unlock writes when you mean to.
• Honest about what cannot be undone. KILL MUTATION stops a mutation but does not roll back what it already wrote. ProbeDeck says so instead of offering a fake Undo.
• Built for mobile networks. Reconnect with backoff, path-aware monitoring of Wi-Fi and cellular handoffs, and specific errors in place of an endless spinner. A ClickHouse error in the response body reads as a query error, not as a dead network.
• A production badge marks each risky action, so you know which cluster you are about to touch.
WHAT YOU CAN DO
• Connect over TLS, an SSH tunnel or a bastion host, with a Face ID app lock.
• Inspect a self-signed or custom-CA certificate fingerprint and accept it per connection.
• Read cluster health at a glance: replicas, disks, parts, merges, mutations and metrics.
• List running queries with elapsed time, memory and the user behind each one.
• KILL QUERY on the query burning the cluster, KILL MUTATION on the one that is stuck.
• Browse databases, tables, columns and DDL.
• Run SQL in the editor and read results laid out for a phone screen.
• Ask the AI assistant why a replica is lagging, through your own Ollama or your own API key.
PRIVACY
• Local-first. Your hosts, passwords, SSH keys and certificates stay on your device, in the iOS Keychain.
• No secrets in logs. ProbeDeck keeps passwords, hostnames, database, table and column names and values out of its logs.
• The AI assistant talks to your Ollama or your key. Nothing reaches us, because we run no server. Schema context is filtered by an allow-list before it goes to a model, and the assistant never executes anything by itself.
• Crash and error reporting is on by default and can be turned off in Settings. Reports are scrubbed and never include hostnames, table names, values or credentials.
• No tracking, no IDFA and no advertising identifiers.
ProbeDeck is foregro
ProbeDeck is built for DevOps, SRE, platform and data engineers on call. Connect over TLS, through an SSH tunnel or a bastion. See cluster health, find the query that is eating the cluster and kill it in seconds, while production credentials never touch someone else's server.
WHY PROBEDECK
• Trust-first. Your credentials stay on your device and never leave it. There is no backend, no proxy, no traffic relay. Your connection goes straight from your phone to your server.
• It knows ClickHouse. Replication lag, read-only replicas and Keeper trouble, parts and merges, "too many parts", stuck mutations, disk pressure. These are the pages you get, so this is the first screen you see.
• Safety on each statement. ProbeDeck classifies your SQL before it sends anything. DROP, TRUNCATE, ALTER UPDATE and ALTER DELETE, DETACH, DROP PARTITION, OPTIMIZE FINAL and KILL need a type-to-confirm step showing the exact target. Costly statements carry a warning. Set a connection read-only and unlock writes when you mean to.
• Honest about what cannot be undone. KILL MUTATION stops a mutation but does not roll back what it already wrote. ProbeDeck says so instead of offering a fake Undo.
• Built for mobile networks. Reconnect with backoff, path-aware monitoring of Wi-Fi and cellular handoffs, and specific errors in place of an endless spinner. A ClickHouse error in the response body reads as a query error, not as a dead network.
• A production badge marks each risky action, so you know which cluster you are about to touch.
WHAT YOU CAN DO
• Connect over TLS, an SSH tunnel or a bastion host, with a Face ID app lock.
• Inspect a self-signed or custom-CA certificate fingerprint and accept it per connection.
• Read cluster health at a glance: replicas, disks, parts, merges, mutations and metrics.
• List running queries with elapsed time, memory and the user behind each one.
• KILL QUERY on the query burning the cluster, KILL MUTATION on the one that is stuck.
• Browse databases, tables, columns and DDL.
• Run SQL in the editor and read results laid out for a phone screen.
• Ask the AI assistant why a replica is lagging, through your own Ollama or your own API key.
PRIVACY
• Local-first. Your hosts, passwords, SSH keys and certificates stay on your device, in the iOS Keychain.
• No secrets in logs. ProbeDeck keeps passwords, hostnames, database, table and column names and values out of its logs.
• The AI assistant talks to your Ollama or your key. Nothing reaches us, because we run no server. Schema context is filtered by an allow-list before it goes to a model, and the assistant never executes anything by itself.
• Crash and error reporting is on by default and can be turned off in Settings. Reports are scrubbed and never include hostnames, table names, values or credentials.
• No tracking, no IDFA and no advertising identifiers.
ProbeDeck is foregro
Latest updates
1.2.7
Test Connection gives up after 10 seconds when the server stays silent and counts the seconds while it waits. In 1.2.6 it could hang for a minute. The dashboard reports a silent server in about 5 seconds, down from several minutes.
After a failed test, the form shows what to check: the port, firewall or VPN if the server never accepted the connection, or a busy server if it connected and sent no reply. Error messages appear in all 11 app languages.
For a ClickHouse Cloud address, the form suggests port 8443 with TLS and sets both in one tap. Paste a full https:// URL into the host field and the app fills in the host, port and TLS. Enter a native protocol port such as 9000 or 9440 and the form offers the matching HTTP port.
In the free version, + opens the ProbeDeck Pro screen once you have a saved connection. That screen has a new Edit Current Connection button, so you can open the saved connection and fix it. If the app cannot reach your server or sign in, the error screen shows Edit Connection next to Retry, and the connection menu has the same item.
If you swipe down a form with unsaved changes, the app asks before it discards them.
Error reports from failed connections include the port, whether you use TLS or SSH, and the kind of address, such as ClickHouse Cloud or a private IP. They never include the name or IP address of your server or SSH bastion. You can turn them off in Settings under Privacy.
1.2.6
On a slow connection, the dashboard and Storage show placeholders while data loads. The status line reads Loading…, and after 3 seconds it shows how long the app has waited for the server. Before this update it read Unknown until the first answer arrived.
Refresh keeps the current values on screen and marks them as updating. Auto-refresh waits for the running request instead of starting a new one every 5 seconds.
Allow local network access in Settings, come back, and the app repeats what failed: Test Connection in the connection form, the monitoring screen, or your last AI question. If you switched AI providers in the meantime, the app does not resend the question.