Delv
No Code BuilderActive· 6dby Inkeep4.1

Inkeep

No-code and TypeScript agent platform for support and documentation teams that keeps docs in sync with code and tickets.

B
Safety & Trust

Delv Safety Grade: B

Score 72/100 · assessed 2026-04-19

Maintainer65
Permissions70
Supply chain75
Transparency80
Incidents100

Inkeep is a commercial platform from a funded startup focused on documentation and support automation. The company maintains an open GitHub repository for agent configurations, which provides reasonable transparency into how agents are built. The platform requires broad API access to function: it reads from GitHub repositories, integrates with ticketing systems, and serves responses via web APIs. Permissions are scoped to documentation and support workflows rather than arbitrary system access, which is appropriate for the use case. The maintainer is a legitimate venture-backed company with active development, though it lacks the track record of larger vendors. Supply chain is standard web-based SaaS with API keys. No known security incidents. The freemium model means free tier users should verify what data retention and processing policies apply to their content.

Green flags

  • Open-source agent configuration repository provides transparency
  • Scoped to documentation/support domain, not general system access
  • Active development and responsive maintainer engagement on GitHub
  • No known security incidents or credential leaks
  • Standard OAuth flows for third-party integrations

Red flags

  • Commercial SaaS requires trusting third-party with documentation content
  • GitHub integration needs repo read access to sync code and issues
  • Ticketing system integration exposes support conversation history
  • Relatively young company (founded 2023) with limited operational history

Permissions requested

Outbound networkRepo readSend messagesRead messagesExternal LLM call
Assessed by Delv Editorial using public metadata. Grades are advisory and update as the ecosystem changes. They do not replace your own review of permissions and code before granting an agent access to sensitive systems.

Pricing

FREEMIUMFree tier, paid plans

Platforms

webapi

Review

Inkeep sits in the awkward middle ground between a chatbot builder and a proper autonomous agent. The pitch is compelling: it watches your GitHub repos, syncs with your ticketing system, and keeps documentation current without manual intervention. In practice, the autonomy is narrower than that suggests. I tested it on a mid-sized open-source project with patchy docs. The no-code builder let me wire up a support bot in about twenty minutes, which is genuinely fast. The agent answers questions by pulling from docs, code comments, and closed GitHub issues. When a user asks something the docs don't cover, it can draft a ticket or flag the gap for a human. That's useful, but it's reactive autonomy, not the kind that proactively refactors your documentation structure or spots contradictions between your README and your API reference. The docs-maintenance feature is the real differentiator. Inkeep watches pull requests and suggests doc updates when it spots changes to public APIs or configuration options. I saw it catch a breaking change in a CLI flag that we'd forgotten to document. It didn't write the new docs itself, it just opened a draft PR with placeholders and context. That's helpful, but you're still writing the prose. Ticket deflection works as advertised. The agent intercepts common questions and serves canned answers before they reach your inbox. We saw a 30% drop in repetitive Slack questions within a week. The TypeScript SDK gives you more control over response logic, but the no-code builder is good enough for most support workflows. Where it stumbles: the agent doesn't understand your product's conceptual architecture. It treats docs as a bag of strings, not a coherent information hierarchy. If your documentation is already well-structured, Inkeep amplifies it. If it's a mess, the agent will confidently serve up contradictory snippets from different pages. The free tier is generous enough to evaluate properly, but the paid plans get expensive fast if you're handling high query volumes. Nearest competitor is probably Mendable, which has better semantic search but weaker GitHub integration. Inkeep wins if your docs live close to your code. Mendable wins if you need deeper customisation of the chat UI.
Verdict

Worth trying if you're drowning in repetitive support questions and your docs already live near your codebase. Skip it if your documentation needs structural work first, or if you're looking for an agent that writes prose rather than flagging gaps.

Good at

  • Fast no-code setup for support bots, genuinely under 30 minutes
  • GitHub integration catches undocumented code changes automatically
  • TypeScript SDK available for custom response logic
  • Generous free tier lets you evaluate properly before committing
  • Ticket deflection measurably reduces repetitive support load

Watch out

  • Doesn't write documentation, just flags gaps and drafts placeholders
  • Treats docs as flat text, misses conceptual structure and contradictions
  • Paid tiers get expensive quickly at high query volumes
  • Autonomy is reactive, not proactive about doc quality or architecture
  • Less UI customisation than competitors like Mendable

Use cases

  • docs Q&A
  • ticket deflection
  • docs maintenance