Connect documents, business data, chat, code, and cloud systems. Give Vedin the knowledge and tools to answer questions and help with the work that follows.
Start with what your team uses today. Available connections and coming-soon plans are marked on every card.
Try another name or clear the filters to see the full catalogue.
Documents and tickets, ready for the next question.
Find the answer in Confluence. Follow through in Jira.
Search and read Confluence pages and Jira issues. Create, comment on, and update Jira issues with the required access.
Your Atlassian URL, account email, and API token. Choose the account’s access before connecting.
Bring shared documents into the answers your team needs.
Sync selected OneDrive or SharePoint documents into Vedin’s knowledge base. Optional document write-back requires the corresponding Microsoft permissions.
Sign in with Microsoft and select folders. A tenant administrator must approve Vedin’s application access before documents can sync.
Business numbers, product trends, and customer feedback.
Ask your business data a question. Get beyond the spreadsheet hunt.
Explore schemas and run read-only SQL across tables. The connection does not grant permission to change your data.
Database details and a read-only database user. Use an in-network agent for a database that is not publicly reachable.
Understand what changed in product usage and conversion.
Explore analytics through PostHog’s MCP tools. The tools exposed by the connection and your credentials determine the available reads and actions.
Connect PostHog through its MCP setup in Vedin and provide the credential requested by the connection wizard.
Bring Android installs, app health, and customer feedback together.
Read install reports, app vitals, reviews, and subscription data when the account has access. These tools do not publish releases.
A service account with the required APIs enabled and permissions granted in Play Console. Install reports require account-wide app access.
Follow iOS installs and reviews alongside your other business data.
Read sales and analytics reports, customer reviews, and subscriptions. Source reports can arrive late; these tools do not publish releases.
An App Store Connect API key, issuer and key IDs, and the appropriate read roles. Sales reports also need your vendor number.
Keep questions, follow-ups, and decisions close to the team.
Ask a question, follow up, or review an approval in the conversation.
Exchange messages with Vedin and respond to clarification and approval cards. This does not import your organization’s entire chat history.
Configure the Vedin Google Chat app for your workspace and link the spaces your team will use.
Drive investigations and approvals where the team already talks.
This connection is not available yet. Planned capabilities:
No release date is promised.
The change, the review, and the context behind it.
Review pull requests with the code and CI results in view.
Read repositories, issues, and workflow results. Enabled tools can post reviews, propose fixes, and trigger workflows, subject to access and action policy.
A GitHub token with the required repository access. Automatic reviews also need a webhook and Auto review enabled for the connection and repository.
Understand a merge request before it becomes a release.
Read projects, merge requests, and pipelines. Enabled tools can post reviews and proposed fixes, subject to access and action policy.
Your GitLab URL and access token. Automatic reviews also need a merge-request webhook and Auto review enabled.
Bring repository knowledge to pull-request reviews and fixes.
Read Bitbucket Cloud repositories and pull requests. Review comments and fix commits require the corresponding write permissions.
Your account email and a scoped Atlassian API token for Bitbucket. Automatic reviews also need a webhook. Bitbucket Server is not supported.
Cloud resources, deployments, and operational signals.
See what is running, what is unhealthy, and what changed.
Inspect workloads, events, and logs. Actions such as restarts need cluster permissions and follow the configured action policy.
An in-network agent in your cluster, with a ServiceAccount and the required Kubernetes RBAC permissions.
Check whether your deployment matches what Git says it should be.
Read application health and sync status. Deployment syncs require sync permission and approval under the configured policy.
An in-network agent, your ArgoCD URL, and an API token. Use separate connections for environments with different access.
Check cloud resources, service health, and recent changes.
Read resource and operational data using the service account’s permissions. Cloud Logging access is needed for log-based analysis.
A Google Cloud service account with read access to the resources you want Vedin to inspect.
Check AWS resource state and recent changes during an incident.
This connection is not available yet. Planned capabilities:
No release date is promised.
Trace an exception to the release and the users it affects.
This connection is not available yet. Planned capabilities:
No release date is promised.
Find the relevant log lines without writing the query.
This connection is not available yet. Planned capabilities:
No release date is promised.
Know who is paged and what the alert timeline looks like.
This connection is not available yet. Planned capabilities:
No release date is promised.
Pull the dashboard context behind an alert into the run.
This connection is not available yet. Planned capabilities:
No release date is promised.
Query time-series metrics and alert state directly.
This connection is not available yet. Planned capabilities:
No release date is promised.
Correlate metrics, logs, and traces in one run.
This connection is not available yet. Planned capabilities:
No release date is promised.
Missing a tool your team relies on? Request an integration
You don’t need to connect everything. Start with the source that can answer your first question.
Add a supported connection in Vedin. Follow its setup flow and grant only the access your team needs.
Choose enabled tools and action policies. For supported private systems, use an in-network agent with outbound connectivity.
Test the connection, then ask a question. Review the answer before handing over a recurring report or check.
A private-network agent connects supported systems. It does not run the full Vedin service or its AI models inside your network. Explore team controls ↗
See what a question or a recurring task looks like for your team.
We’ll send you a link to get started.