Works with what you already run.
Every integration is listed with where it stands today. Reads run freely; anything that sends or changes waits for a named person.
PelQi Work, in the pilot
- Web searchPublic pages and news, read only, with every source cited.Available
- PelQi’s own browserAn isolated browser that can reach the public internet only. It reads pages, never types or buys, and keeps a screenshot of each.Available
- Microsoft 365Outlook mail and calendar. Each person connects their own mailbox; PelQi reads and prepares drafts, and sends only after the mailbox owner approves.New
PelQi in Varqeni, in the Fortis lab
PostgreSQLReplication slots and the heartbeat table, through identities that can only read.Lab
Apache KafkaKafka Connect connectors and tasks, and broker health.Lab
KubernetesPods, restarts, cluster events and worker logs.Lab
PrometheusPlatform and estate metrics for the whole lab.Lab
PelQi Home
- Local businesses on Fortis FountainPelQi asks a business for you, and only after you approve the message.Available
- Travel searchesHotels, homes and cars open with your details filled in; you book and pay with the provider.Available
Next
- Jira and ConfluenceEach person connects their own Atlassian account. PelQi searches issues and pages; a comment or new issue waits for that person’s approval.Soon
- Zoho CRMEach person connects their own Zoho account. PelQi reads deals, accounts and contacts; a new task or deal update waits for that person’s approval.Soon
- Microsoft TeamsTalk to PelQi Work where your team already is.Next
- Varqeni in PelQi WorkOperations summaries from Varqeni inside the business view.Next
As yourself. Nothing more.
You sign in to each system with your own account, and PelQi works with exactly what that account can see. It reads freely, prepares the rest, and waits for a person before anything is sent or changed.
How connections work.
Your own sign-in
Each person connects their own account. PelQi sees what that person can see, and a responsibility uses its owner’s connection.
Kept sealed
Sign-ins are stored encrypted and never shown again, not even to PelQi’s own tools. Disconnect at any time.
Least access
Platforms get identities that can only read, proved when they are created. Business actions are drafted and wait for approval.
Missing a system you run?
Tell us on the waitlist which system PelQi should learn next. It shapes the order we build them in.
PostgreSQL, Apache Kafka, Kubernetes and Prometheus are trademarks of their respective owners; their logos indicate compatibility. Microsoft 365, Outlook, Teams, Jira, Confluence and Zoho CRM are trademarks of their owners. PelQi connects through their published interfaces with your own accounts; no partnership or endorsement is implied.