For the CTO and the head of data
We review your databases in read-only mode and tell you what would bring them down the day real customers arrive, with the evidence for each point.
You get the report with the risk indicators and a baseline to compare against. Scope and timeline are in writing before we start.
Updated on
You don't need it if the system is a trial with little data that is not going to grow.
With test data everything responds instantly. With thousands of customers and years of data you get the queries that take seconds because of a missing index and the connections that run out at peak. It almost always gives warning first, if someone is looking. According to CIO Dive, reporting on an S&P Global Market Intelligence survey (2025), organizations scrapped on average 46% of their AI proofs of concept before they reached production.
46%
AI proofs of concept scrapped before production
S&P Global Market Intelligence, 2025More than 200 control points
Trademarks and logos belong to their respective owners. Their use here is descriptive only and implies no commercial relationship or sponsorship.
In 30 minutes we look at which engines you use and how much you expect to grow. Then you get in writing what is reviewed, what is left out and the timeline.
We read the structure, the queries and the configuration of each engine. The review changes nothing in your running system.
You get the risk indicators with their evidence and a baseline, and we go through it with your team. The next review is compared against it.
Priority: Medium
Order search by customer with no index
An example of the report format, not a client's.
Shall we talk about your case?
A 30-minute meeting to see what you have and what to review first.
All three are useful, each for one thing. AI brings the volume and people bring the judgment: that is why our review uses an automated AI tool and senior developers supervise it.
The review is done by a team of senior developers, with many hours of development and of finding the mistakes AI makes when it codes. We know more than 1,200 review points. The automated AI tool goes through them, and people verify, direct and review.
Team of senior developers
José María Salido, founder of Sondeon, answers for it
We review PostgreSQL, Redis and compatible engines (Valkey, Dragonfly, KeyDB), Elasticsearch or OpenSearch, and RabbitMQ. Other engines are looked at case by case in the meeting.
No. The review only reads: it changes no data, tables or configuration. The changes we propose go in the report so you decide which ones are applied.
A read-only user on each engine and read access to the code that uses the database. What we ask for is written into the scope before we start.
We measure first: slow queries, indexes that are missing or that nothing uses, locks and memory. The fix is separate and only if you ask: your team applies it with the report, or we do with the changes you approve.
The 30-minute meeting is free. The rest depends on how many engines are included and on the size of the data. We go over it in that meeting, and you get the scope and timeline of our health check in writing before we start.
It is a review of how the database is set up and how it responds: indexes, slow queries, locks, memory and queues. It is not the log of who did what inside the engine. Our health check is read-only and runs before going to production and every three months, because data grows.
Flutter apps built with AI, tested on real iOS and Android phones by command and with touch gestures, together with their backend.
Your website's performance, visibility in search engines and in AI assistants (SEO and GEO), accessibility and security, measured on the real page.
The server side behind your app or your website: what the API exposes, what it protects, what headers it serves and what ends up in its logs.
The server your system will run on, reviewed before you go live: who has access, what runs on it and which limits break as you grow.
The Linux machines your system runs on, measured every few seconds, so you see a full disk or a stopped container before your users do.
Every call to your API measured, with its latency, its error and the screen that requested it, so you know which endpoint to optimize before traffic grows.
Fill in the form and we email you to set a day and a time. It is 30 minutes to see what you have and what to review first.
