Your Rails app already knows the answer. Now anyone can ask it.
Adea reads your models, enums and scopes and connects them to your database. Sales and support can ask "how many orders did we get in September?" and get a number that follows your own rules.
How many orders did we get in September?
- Reading app/models/order.rb
- Finding enum status: completed
- Counting orders in September
How many orders did we get in September?
4,812orders
Only orders with status completed are counted. Most in the Dogs category (1,904).
Where the number comes from
The code Adea read app/models/order.rb:15
enum :status, { pending: 0, paid: 1,
cancelled: 2, completed: 3 }The query it ran
SELECT count(*) FROM orders WHERE status = 3 AND completed_at >= '2026-09-01' AND completed_at < '2026-10-01'
What you get
Understands your enums and scopes
In Rails the business rules live in the models. Adea reads them, so "completed" means to Adea what it means to your code, not what a colleague guesses.
From question to true number
Every query is a single read query with a time limit. You see the SQL, the file and the line the number is built on.
Developers approve the rules
The first time Adea learns that an order counts at completed, a developer can approve it with one click. After that the rule is used in every answer.
How to connect a Rails app
Give Adea read access to the repo through GitHub, and create a database user that can only read. It takes a few minutes.
CREATE ROLE adea_readonly LOGIN PASSWORD '…'; GRANT SELECT ON ALL TABLES IN SCHEMA public TO adea_readonly;Read the setup guide
Questions about Rails
Does Adea need changes in the app?
No. Adea reads the code and a read replica of the database. Nothing is installed in your Rails app.
Does it work with Rails 6, 7 and 8?
Yes. Adea reads the code as it is and follows your models, enums, scopes and concerns whatever the version.
What about PostgreSQL or MySQL?
Both. We recommend a read replica, so questions never load production.