Shared knowledge base
Upload files, write documents, and organize the knowledge your workspace uses to answer questions and investigate problems.
A closer look at
what Vedin can do.
Start with a question. Connect another tool. Hand over a recurring task. Explore the capabilities your team can put to work.
26 features
Features depend on your workspace setup, connected sources, and permissions.
No matching features. Try a different search or clear the filters.
Knowledge
Give your team’s knowledge a place to grow.
Document revisions
Review how a document has changed and restore an earlier version when you need it.
Knowledge graph
Explore connections between documents and generated system knowledge. Follow relationships to see what belongs together.
Dream Cycles
Keep the connections in your knowledge graph useful. Dream Cycles strengthen well-used links, discover related knowledge, and prune weak links on a schedule.
How it works
Administrators can set the schedule, pause cycles, and revert recorded automatic changes. Uncertain connections become questions; proposed directional relationships, such as dependencies, require confirmation. Pinned links are protected from decay and pruning.
Help Vedin
Answer questions about missing knowledge or uncertain connections. Confirm what is right, pin a relationship worth remembering, or reject a suggestion.
How it works
Dream Cycles maintain knowledge relationships. They do not train the underlying AI model or automatically fix your systems.
Answers & analysis
Ask the question, then follow it where it leads.
Answers from shared knowledge
Ask in plain language. Vedin searches the knowledge available in your workspace and can read the documents behind an answer.
Data analysis and charts
Explore connected business data and turn results into summaries, tables, and charts.
How it works
Results depend on available data. Review gaps and assumptions; a generated analysis is not a validated forecast.
Chat and follow-ups
Ask in Vedin or Google Chat, then continue the conversation using the earlier thread as context.
How it works
A connected chat channel is not automatic ingestion of all chat history.
Engineering
Understand the systems you have and the changes ahead.
Code search and navigation
Ask about indexed repositories, find definitions and references, and trace call chains without piecing everything together by hand.
Architecture and repository knowledge
Use generated repository documentation and cross-repository relationships to understand how services fit together.
How it works
Coverage depends on connected repositories and successful indexing.
Code reviews and proposed fixes
Review pull requests with repository context and your documented conventions in view. Use proposed fixes as a starting point for your review.
How it works
Review and test proposed changes before merging or deploying them.
Vedin MCP
Give compatible coding assistants access to your Vedin knowledge. Search and read documents from tools such as Claude Code, Codex, and Cursor.
How it works
Vedin’s knowledge MCP server is read-only. Access requires an enabled endpoint and a personal token; it stays within the token owner’s permitted knowledge scope. Tokens can expire or be revoked.
Automations & investigations
Hand over the repeat work. Come back to the result.
Scheduled tasks
Describe recurring work and choose a schedule. Have Vedin prepare reports, perform a triage sweep, or carry out a task using connected tools.
How it works
Each run has a recorded status and result. Available tools, permissions, and usage limits still apply.
Scheduled checks
Set up repeatable pass/fail checks for supported conditions, such as an HTTP response, certificate expiry, or database row count.
How it works
Checks use a saved execution plan. Depending on configuration, failures can trigger adaptation or an investigation.
Run history and schedule controls
See what ran, what happened, and the recorded usage. Pause recurring work when it is no longer needed.
Investigations from questions and alerts
Start from a problem or a supported alert webhook. Vedin gathers evidence with connected tools, records findings, and works toward a next step.
How it works
Connect a supported alert source to start investigations automatically. Review recorded evidence before applying a proposed fix.
Runbook execution
Use structured runbook documents to guide repeatable work through Vedin’s tools.
How it works
Execution depends on supported runbook steps, enabled tools, and applicable action policies.
Connections & custom tools
Bring the systems your team already relies on.
Connected business and engineering tools
Connect supported document sources, chat, databases, code hosts, and cloud systems. Use their knowledge and tools in the same workflow.
How it works
The integration catalogue distinguishes available connections from those coming soon.
MCP server connections
Bring tools into Vedin from an internal or third-party Model Context Protocol server. Configure the server, discover its tools, and test the connection.
How it works
Vedin calls tools provided by the connected server. Available actions depend on the server’s tools, authentication, and configured permissions.
Custom tools
Connect internal APIs, scripts, and other supported tool types when a built-in integration does not cover your workflow.
How it works
Configure what the tool does, test it, and assign an approver when a person must review its use.
Reusable variables
Reference named values in tool configurations and task prompts. Keep environment-specific settings separate from the work you want to run.
Private-system access
Use an infrastructure agent to connect supported systems inside your network, including private databases and infrastructure tools.
How it works
The agent provides access to supported systems. It does not self-host the complete Vedin service or its AI models.
People & controls
Keep people involved where their judgment matters.
Action approvals
Review actions that require your approval before they run. See the proposed action and its context, then approve or reject it, with the decision recorded.
How it works
Approval requirements depend on the tool’s action policy, approver, and connection permissions.
Clarifying questions
When Vedin needs information from you, answer in the workflow so it can continue with the missing context.
Inspectable work
Review recorded findings, tool calls, outputs, and approval decisions. See what Vedin tried and where it needs more help.
Workspace permissions
Manage who can invite people, maintain knowledge, configure connections, and manage tools in your organization’s workspace.
How it works
Access to a connection does not bypass its credentials or execution policy.
See the pieces at work.
Walk through the product, or start with the work your team needs help with.