Skip to content

SOLUTIONS · PRODUCT AND TECH

Your code, your data and your app reviews, in your AI

Code, database, Redash queries, store reviews, subscriptions, logs: each tool is connected once, without credentials for every member.

An incident, a metric that drops, a campaign to compare: the assistant cross-checks the sources and cites what it read.

Have payment errors gone up since last night? If so, which deployment lines up?

Yes: 214 failed payments since 9 pm, against about forty over the same period the day before. The rise starts at 9:08 pm, two minutes after the api-payments application was deployed. From that time, the logs show a timeout error towards the payment provider.

Sources consulted

  • PostgreSQL · payments table · read
  • Clever Cloud · api-payments · deployments and logs
Example exchange, fictional data.

ACCESS

Everyone only sees what concerns them

  • Chosen tables

    A PostgreSQL database is opened table by table. The rest of the schema does not exist for the assistant.

  • Approved queries

    On Redash, the assistant only reads the queries an administrator opened, with no free SQL.

  • Hosting without the console

    Clever Cloud deployments, logs and metrics are read per application, with no access to the console or to secrets.

SETUP

Up and running in three steps

  1. Connect the sources

    An administrator connects PostgreSQL, Redash, Purchasely or Clever Cloud once. Credentials are encrypted and never shown to members.

  2. Open them to each team

    They pick the tables, queries and applications opened to each team. The rest is invisible to that team's assistant.

  3. Ask the question

    The member queries their sources from their assistant, for instance to read a database read-only, explain an MRR drop or understand a production incident.

CONNECTORS

The connected tools

IN PRACTICE

Use cases, step by step

Questions

Frequently asked questions

Do we have to give credentials to every member?

No. An administrator connects the database, Redash or Clever Cloud once; members query what is opened to them, without credentials.

Can the assistant write to the database?

No. Only bounded SELECT queries run: 200 rows and 60 seconds per query, no writes.

What about the app’s subscriptions?

Purchasely connects with a read-only key: revenue, subscribers, paywall conversion and A/B tests are read per app, with no Purchasely account for each member.

What about source code?

GitHub and GitLab connect too: the assistant reads the synced repository, without cloning it, with the same rights per team.

CUSTOMERS

What our customers say.

ADN

“A question that used to take the data team a week, every team now asks its own AI.”

Julien Lemoine · CEO, ADN

  • ClickHouse
  • Batch
  • Agorapulse
Read the ADN story
STS

“We connected our tools once. Production checks payroll, product triages errors, account managers review their portfolio: each from their own AI, on their own tools only.”

Julien Hay · CTO, STS

  • Silae
  • Redash
  • Sellsy
  • Aircall
  • Sentry
Read the STS story

Connect one tool. The whole team asks away.

Connect a first tool and try Persyst for free with your team for 14 days.

You use your existing AI assistant subscription.