Thally Reviews and Details

Questions & Answers

1. Who are some of the biggest customers of Thally?

   • Hackmamba.io — design partner
   • Procta.org — design partner
   • LI.FI — design partner

   Others:

   Hexdocs Schemaport Seamline

2. What makes Thally unique?

   Thally connects changes in your code to the information people use to understand your product. When an API, feature, or workflow changes, it finds the affected content across connected docs, websites, support articles, and examples, then opens pull requests with the updates and supporting evidence.

   Your team gets the investigation and proposed fixes together, ready for review. That keeps outdated information from spreading to developers and the AI assistants building with your product.

3. Why should a person choose Thally over its competitors?

   Choose Thally if keeping content accurate takes more effort than publishing it. You get a complete documentation platform alongside automation that tracks product changes and prepares updates across connected content.

   Managed hosting, search, AI answers, previews, and rollbacks come together in one platform. Developers and AI tools access the same source of knowledge, and your team approves what gets published. Your content stays in your repositories, with an open-source engine you can self-host.

4. How would you describe the primary audience of Thally?

   Software teams whose products change faster than their documentation can keep up. Thally is built for developers, technical writers, DevRel teams, and product teams maintaining API products, SDKs, developer tools, and SaaS platforms, especially when product knowledge is spread across multiple repositories and websites.

5. Which are the primary technologies used for building Thally?

   Netlify - Netlify has been part of my own developer-experience journey, so I knew what a great shipping workflow should feel like before building Thally. Its Git-based workflow and deploy previews give us a reliable, low-friction way to ship Thally Cloud while we focus our time on the product.

   Neon - Neon gave us the managed Postgres foundation we wanted without making database operations another thing to babysit. It kept the data layer lightweight while we iterated on Thally’s workspaces, repositories, and change-analysis pipeline.

   Resend - Resend let us add product email without turning email infrastructure into a side project. Its developer-first API and straightforward setup made it easy to support onboarding and workflow notifications while keeping our small team focused on Thally’s core product.

   Cloudflare - Cloudflare was the right fit because Thally needs to publish and rebuild customer-facing knowledge quickly without us operating a large infrastructure stack. Workers and Cloudflare for Platforms give us a path to isolated deployments, global delivery, and a release workflow we can control.

   Thally’s documentation engine is built on Next.js, with Markdown and MDX for content and Git-based workflows for version control and review. It publishes content as web pages and machine-readable formats, including Markdown and JSON, with Model Context Protocol (MCP) support for AI tools. The engine is MIT-licensed and supports self-hosting.

6. What's the story behind Thally?

   Thally grew out of a problem its founder, Ekene Eze, faced while working in developer experience at Flutterwave, Netlify, and LI.FI. Every release meant chasing product context, inspecting code changes, and finding every guide, example, and public page that needed updating.

   As AI assistants began using that same content to generate code, outdated information could spread further and cause more broken integrations.

   Ekene created Thally to take that investigation off teams’ plates. It traces product changes across connected content and opens pull requests with proposed updates and supporting evidence, ready for the team to review.