Table of Contents
- 1. GitBook
- Key Strengths & Use Cases
- Pricing, Pros & Cons
- 2. ReadMe
- Key Strengths & Use Cases
- Pricing, Pros & Cons
- 3. Mintlify
- Key Strengths & Use Cases
- Pricing, Pros & Cons
- 4. Redocly
- Key Strengths & Use Cases
- Pricing, Pros & Cons
- 5. Document360
- Key Strengths & Use Cases
- Pricing, Pros & Cons
- 6. Atlassian Confluence (Cloud)
- Key Strengths & Use Cases
- Pricing, Pros & Cons
- 7. HelpDocs
- Key Strengths & Use Cases
- Pricing, Pros & Cons
- 8. Slab
- Key Strengths & Use Cases
- Pricing, Pros & Cons
- 9. Read the Docs (Community + Commercial)
- Key Strengths & Use Cases
- Pricing, Pros & Cons
- 10. Docusaurus (open source)
- Key Strengths & Use Cases
- Pricing, Pros & Cons
- 11. MkDocs (open source)
- Key Strengths & Use Cases
- Pricing, Pros & Cons
- 12. Notion (for internal docs and wikis)
- Key Strengths & Use Cases
- Pricing, Pros & Cons
- Top 12 Software Documentation Tools: Feature Comparison
- Final Thoughts
- Key Takeaways and Decision-Making Framework
- Your Action Plan for Selecting a Tool
Slug
software-documentation-software
Excerpt
Discover the 12 best software documentation software tools. Our guide covers features, pricing, and use cases to help you find the right fit for your team.
Great software is built on great communication, and nowhere is that more critical than in your documentation. Choosing the right software documentation software is a foundational decision that impacts everything from developer onboarding and user adoption to customer support efficiency. The wrong tool creates friction, hides information, and wastes valuable time. The right one becomes a single source of truth that empowers your entire team and user base.
This guide is designed to help you bypass the endless "free trial" loop. We've compiled a detailed analysis of the top platforms available, cutting straight to the information you need to make a confident choice. You won't find marketing fluff here, just a practical breakdown of what each tool does best and where it falls short.
For each option, we provide a clear overview covering:
- Key Features: A focused look at critical functions like search, version control, and access management.
- Ideal Use Cases: Who is this platform built for? Is it for public APIs, internal knowledge bases, or user guides?
- Pros & Cons: An honest assessment of strengths and limitations based on real-world application.
- Pricing: A simple summary of their pricing structure.
We've included screenshots and direct links for every tool, from open-source powerhouses like Docusaurus to dedicated SaaS solutions like GitBook and Document360. Our goal is to equip startups, small businesses, and developers with a clear roadmap to finding the perfect documentation platform for their specific needs, saving you time and preventing costly mistakes. Let's find the right fit for your project.
1. GitBook
GitBook has established itself as a leading hosted documentation platform, prized for its speed and simplicity. It removes the technical overhead of traditional static-site generators, allowing teams to create and publish polished public product docs or internal knowledge bases with minimal friction. Its AI-native features, including a writing assistant and the "GitBook Agent" for contextual suggestions, position it as a modern piece of software documentation software that helps teams write better content, faster. The platform’s standout feature is its seamless Git synchronization, which lets developers treat documentation as code, managing updates through pull requests and maintaining version history across different branches.
Key Strengths & Use Cases
GitBook shines for startups and scale-ups that need to ship documentation quickly without dedicating engineering resources to maintenance. The user experience is clean and the search function is exceptionally fast, which significantly improves reader engagement. Its granular access controls are a major benefit, enabling teams to manage public, private, and internal content within a single space using private share links or SAML SSO for enterprise-grade security.
Pricing, Pros & Cons
GitBook's pricing is structured per user and per "space" (a documentation site). The free tier is generous for open-source projects. Paid plans add features like custom domains, advanced access control, and deeper analytics.
- Pros: Very low setup burden, modern UX with fast search, granular access controls for mixed public/private docs.
- Cons: Limited theming compared to open-source alternatives, and costs can escalate for large teams or numerous documentation sites.
2. ReadMe
ReadMe is laser-focused on creating an exceptional developer experience, specifically for API documentation. It goes beyond static text by providing an interactive developer hub where users can make real API calls directly from the documentation. The platform is built for speed, allowing teams to quickly ship a branded, interactive portal complete with guides, API references, and changelogs. With features like Ask-AI assistance and support for MDX, developers can embed rich React components, making ReadMe a powerful piece of software documentation software for API-first companies.
Key Strengths & Use Cases
ReadMe excels at building comprehensive developer portals that merge reference docs with marketing content. Its standout feature is the interactive API explorer, which is generated from an OpenAPI (Swagger) specification and allows developers to test endpoints without leaving the page. This is ideal for SaaS businesses whose primary product is an API. The platform also offers a Developer Dashboard add-on, which provides valuable analytics by tracking API usage and logs, helping teams understand how their API is being used in the wild.
Pricing, Pros & Cons
ReadMe’s pricing is based on features and projects. The Startup plan covers the essentials for one project, while Business and Enterprise tiers add advanced security, customization, and multi-project management. The analytics and logs dashboard is a separate, usage-based add-on.
- Pros: Superb out-of-the-box interactive API reference, enables non-technical writers to contribute easily, strong enterprise features for security and scale.
- Cons: Pricing can become substantial on Business/Enterprise plans, and the valuable API logs analytics feature comes at an additional cost.
3. Mintlify
Mintlify is a hosted documentation platform that has quickly become a favorite among developer-focused companies. It excels at creating beautiful, fast, and feature-rich documentation sites with almost no infrastructure overhead. The platform is built around a Git-backed workflow using MDX, allowing developers to write documentation with components, but also offers a user-friendly web editor for non-technical contributors. Its standout features, including interactive API playgrounds, built-in styling checks, and an AI writing assistant, make it a powerful piece of software documentation software for teams that want a premier user experience without the hassle of building it themselves.
Key Strengths & Use Cases
Mintlify is ideal for developer-tool companies and API-first businesses that need to present technical information in a clean, interactive format. Its out-of-the-box design is exceptionally polished, saving teams from extensive front-end work. The integrated API playgrounds allow users to make real API calls directly from the documentation, which greatly improves the developer onboarding experience. Features like preview deployments for pull requests and custom authentication options make it a reliable choice for professional teams that need to move fast while maintaining high quality standards.
Pricing, Pros & Cons
Mintlify's pricing is user-centric, with a generous free plan for open-source and small projects. The Pro plan is aimed at funded teams and adds crucial features like custom authentication, a dedicated success manager, and enterprise-grade SLAs.
- Pros: Excellent out-of-the-box design, strong API reference experience with interactive components, minimal setup for a fast launch.
- Cons: Pro plan pricing can be steep for smaller companies, and being a hosted platform limits deep customization compared to self-hosted alternatives.
4. Redocly
Redocly specializes in API-first documentation, offering a suite of tools built around OpenAPI specifications. It provides a robust, high-performance rendering engine that creates the familiar three-panel API documentation layout that developers know and love. This makes Redocly an excellent piece of software documentation software for companies whose products are heavily reliant on APIs. The platform focuses on turning complex API specs into clean, interactive, and highly performant documentation sites, complete with a “Try it” console for real-time endpoint testing.
Key Strengths & Use Cases
Redocly is the perfect fit for organizations that need to manage a large catalog of APIs and demand enterprise-grade governance. Its advanced search, version switcher, and options for private labeling or even self-hosting on-premise cater to complex security and branding requirements. The developer experience is a primary focus, ensuring that the final documentation is not just accurate but also genuinely useful and fast for the engineers consuming the API.
Pricing, Pros & Cons
Redocly’s pricing reflects its enterprise and developer focus, scaling with features like SSO, governance, and support. While a basic open-source renderer is available, the full platform is a premium offering compared to simpler static site generators.
- Pros: Optimized, fast API docs UX that developers recognize, scales from single specs to large API catalogs, mature governance and SSO options on upper tiers.
- Cons: Pricing is higher than basic static setups, and a recent product line transition means some users may need to plan for migration from older tools.
5. Document360
Document360 is a mature, enterprise-focused knowledge base platform designed for creating extensive customer-facing help centers and internal standard operating procedures (SOPs). It excels at managing documentation across multiple products or versions from a single portal, making it a strong choice for companies with complex support needs. As a piece of software documentation software, its power lies in its robust back-end features, including AI-powered search, detailed analytics on article performance, and structured content workflows with review and approval stages. The platform balances a user-friendly editor with the governance required by larger organizations.
Key Strengths & Use Cases
Document360 is built for support and success teams that need to reduce ticket volume with a self-service knowledge base. Its capacity to manage multiple private or public projects is ideal for companies supporting a portfolio of products. The platform includes powerful importers to help with migration from other systems, and its reader feedback and analytics tools allow teams to continuously improve article quality. The availability of 30+ integrations and enterprise-grade security like SOC 2 compliance and SSO makes it a safe bet for regulated industries. For more insights on building out a support-focused resource, you can find other top-tier knowledge base software options to compare.
Pricing, Pros & Cons
Document360's pricing is primarily quote-based and tailored to specific business needs, reflecting its enterprise focus. Plans vary based on the number of team accounts, knowledge bases, and article versions required.
- Pros: Strong enterprise readiness (SOC 2, SSO, audit trails), excellent migration and onboarding support, flexible structure for multi-KB and multi-product environments.
- Cons: Pricing is not publicly transparent, and theming customization is more limited than code-based static site generators.
6. Atlassian Confluence (Cloud)
Atlassian Confluence is less a dedicated documentation portal and more a comprehensive team workspace where documentation is a core function. It thrives in environments already committed to the Atlassian ecosystem, offering unmatched integration with Jira. This makes it a powerful piece of software documentation software for teams that need to link technical specs directly to development tickets, project plans, and team-wide announcements. Confluence bridges the gap between engineering and business teams, providing a unified space for everything from product requirements to HR policies. Its strength lies in its structured, wiki-like nature and deep collaborative features.
Key Strengths & Use Cases
Confluence is the default choice for enterprises that need robust governance, permissions, and audit trails. Its structured page trees, templates for meeting notes or project plans, and powerful macros allow for highly organized and standardized content creation. The platform is ideal for internal knowledge bases where collaboration across departments is constant. Deep Jira integration allows teams to embed and automatically update issue statuses within documentation pages, creating a single source of truth that connects planning with execution. This is critical for maintaining an effective knowledge management strategy in a large organization.
Pricing, Pros & Cons
Confluence's pricing is per-user, with a free tier for up to 10 users that includes most core features. Paid plans add granular permissions, unlimited storage, and enterprise-grade security features like SAML SSO and data residency.
- Pros: Unbeatable Jira integration, strong governance and admin controls, and excellent for internal cross-team collaboration.
- Cons: Public-facing sites feel less polished than dedicated tools, the user interface can feel dated, and per-user costs can become significant as a company scales.
7. HelpDocs
HelpDocs is a hosted knowledge base platform designed specifically for customer-facing help centers. It focuses on simplicity and speed, enabling support and content teams to publish articles with an intuitive, non-technical workflow. While it can function as a form of software documentation software, its core strength lies in deflecting support tickets. The platform is increasingly integrating AI, offering features like AI-powered drafts, content rewrites, and style enforcement, which helps teams maintain consistency and produce content more efficiently. It’s built for teams who need a functional, user-friendly help center without a complex setup.
Key Strengths & Use Cases
HelpDocs is ideal for SaaS companies and e-commerce businesses aiming to reduce their customer support load. The quick setup and straightforward editor empower non-technical team members to create and manage content effectively. Its built-in multilingual support and embeddable widget are significant advantages for reaching a global audience and providing contextual help directly within an application. For more visual control, the platform allows for complete templating with custom CSS, JavaScript, and HTML, while higher-tier plans offer enterprise features like SAML SSO.
Pricing, Pros & Cons
HelpDocs prices its plans based on the number of articles and user seats, with AI features tied to a credit system. A free trial is available to test the platform. Paid plans unlock features like custom domains, API access, and multilingual support.
- Pros: Very quick setup with an intuitive editor, built-in multilingual and widget options are great for customer support, and reasonably priced for smaller teams.
- Cons: Limited developer-centric workflows compared to Git-based tools, and AI credits are capped on each plan, requiring careful management.
8. Slab
Slab positions itself as a modern internal wiki and knowledge hub, built around the principles of fast search, content verification, and a minimalist writing environment. While not a conventional tool for external-facing developer docs, it excels as an internal software documentation software for centralizing team knowledge, onboarding materials, engineering playbooks, and company policies. It prioritizes a clean, uncluttered interface that encourages adoption and makes it simple for anyone to contribute, bridging the gap between technical and non-technical teams. Its strength lies in being the single source of truth that is easy to maintain.
Key Strengths & Use Cases
Slab is ideal for internal knowledge management where clarity and discoverability are paramount. Features like content verification allow owners to mark documentation as up-to-date, building trust across the organization. It integrates with popular tools like Slack, GitHub, and Asana, bringing context directly into the platform. Its topic-based structure provides a more intuitive organization than traditional folder hierarchies, helping users find related information quickly. For engineering teams, it's a great place for runbooks, post-mortems, and architectural decision records.
Pricing, Pros & Cons
Slab offers a generous free tier for up to 10 users, making it accessible for small teams and startups. Paid plans add SSO/SCIM, advanced analytics, and API access. Pricing is based on a per-user model, which is standard for the category.
- Pros: Exceptionally clean and intuitive UX, strong content verification and governance features, generous free plan.
- Cons: Not designed for public-facing API documentation or interactive code examples, limited customization compared to dedicated developer portals.
9. Read the Docs (Community + Commercial)
Read the Docs is a cornerstone of the open-source documentation world, offering free, automated hosting for projects built with popular static-site generators like Sphinx (for Python) and MkDocs (for Markdown). It automates the entire build and deployment process by pulling directly from Git repositories (GitHub, GitLab, Bitbucket), making it a go-to choice for engineering teams who treat documentation as code. For these teams, it stands out as a powerful piece of software documentation software by providing automated versioning, pull request previews, and stable hosting without any server management overhead.
Key Strengths & Use Cases
Read the Docs is the ideal solution for code-adjacent documentation where CI/CD-like workflows are paramount. Its ability to automatically build and host different versions of your docs (e.g., stable, latest, or feature branches) is a critical feature for software libraries and APIs. The platform handles traffic spikes and content delivery for some of the largest open-source projects, proving its reliability at scale. The commercial offering extends these benefits to private repositories, adding team management, ad-free sites, and enhanced support for businesses.
Pricing, Pros & Cons
The Community version is free for public, open-source projects and is supported by ads. Read the Docs for Business offers paid plans for private projects, with pricing based on the number of projects and users. The paid tiers are affordable, starting with a plan for small teams.
- Pros: Excellent for code-adjacent docs with CI-like workflows, zero hosting to manage, and a completely free tier for open-source projects.
- Cons: Not a WYSIWYG editor; requires comfort with Sphinx or MkDocs. Theming and customization complexity depends entirely on the underlying static-site generator and its theme ecosystem.
10. Docusaurus (open source)
Docusaurus is a powerful, open-source static site generator from Meta, built with React. It empowers teams to create content-focused documentation sites with modern web capabilities and full control over the final product. By treating documentation as code, it fits perfectly into a Git-based development workflow. Its support for MDX (Markdown with JSX) allows authors to embed interactive React components directly within their content, making it an excellent piece of software documentation software for creating dynamic and engaging guides.
Key Strengths & Use Cases
Docusaurus excels for organizations that prioritize deep customization and ownership of their documentation platform. It's ideal for projects requiring robust versioning for multiple software releases and internationalization (i18n) to reach a global audience. The plugin and theming ecosystem offers extensibility, while the ability to deploy the static output to any host (like Netlify, Vercel, or GitHub Pages) keeps infrastructure costs extremely low. It is a fantastic choice for scaling documentation across multiple products under a unified brand.
Pricing, Pros & Cons
As an open-source project, Docusaurus is completely free to use. Costs are limited to hosting, which is often free or very inexpensive for static sites. The primary investment is the engineering time required for setup and maintenance.
- Pros: Maximum control over UX, theming, and performance; no vendor lock-in; host cheaply or on existing infrastructure; scales well for multi-product documentation.
- Cons: Requires frontend familiarity and a build pipeline; the authoring experience is less WYSIWYG for non-developers.
11. MkDocs (open source)
MkDocs is a fast, simple static site generator that’s geared specifically for building project documentation. Written in Python, it allows you to write documentation in Markdown and configure your site's layout and navigation with a single YAML file. This approach positions it as a go-to piece of software documentation software for developer-centric teams who prefer a docs-as-code workflow without the complexity of larger frameworks. It is lightweight, fast, and integrates seamlessly into CI/CD pipelines for automated deployments.
Key Strengths & Use Cases
The real power of MkDocs lies in its simplicity and the extensive plugin ecosystem, most notably the popular "Material for MkDocs" theme. This theme adds a modern, responsive design and a wealth of features like search, versioning, and social cards with minimal configuration. It is ideal for open-source projects, internal API documentation, and technical blogs where the content is managed in Git and authored by developers comfortable with Markdown. Deployment is straightforward to services like GitHub Pages, GitLab Pages, or Cloudflare Pages.
Pricing, Pros & Cons
As an open-source project, MkDocs is completely free to use. Costs are limited to hosting, which can be free for public repositories on platforms like GitHub Pages.
- Pros: Extremely fast local builds, simple YAML configuration, mature plugin ecosystem, and a powerful out-of-the-box experience with the Material theme.
- Cons: Requires comfort with the command line and Markdown; lacks a built-in WYSIWYG editor for non-technical contributors.
12. Notion (for internal docs and wikis)
While not a purpose-built documentation platform, Notion has become the de facto internal wiki and knowledge base for countless startups and tech companies. Its power lies in its all-in-one workspace approach, where databases, documents, and project boards coexist seamlessly. This makes it an incredibly low-friction choice for internal software documentation software, as teams are often already using it for daily operations. Features like content verification, which allows owners to confirm page accuracy, and robust relational databases make it perfect for creating interconnected systems of information, from technical runbooks to employee handbooks.
Key Strengths & Use Cases
Notion excels for internal documentation where speed of creation and team-wide adoption are paramount. Its flexible, block-based editor is intuitive for non-technical team members, making it easy for anyone to contribute. Many organizations use it to centralize everything from engineering SOPs to marketing playbooks. While its native public site capabilities are basic, you can create a more advanced knowledge base by using third-party tools that add custom domains and better styling to published Notion pages.
Pricing, Pros & Cons
Notion offers a free personal plan, with paid plans adding team collaboration features, increased storage, and security options like SSO. Pricing is per user, per month, making it accessible for teams of all sizes.
- Pros: Extremely fast to author and adopt across non-technical teams, flexible structure suitable for handbooks and SOPs, ideal if your organization already uses it for projects.
- Cons: Not a dedicated API-docs tool (no built-in interactive console), and public-site theming is basic without a front-end layer.
Top 12 Software Documentation Tools: Feature Comparison
Product | Core features ✨ | UX & Quality ★ | Value & Pricing 💰 | Best for 👥 | Unique selling points 🏆 |
GitBook | Git sync, AI writing, SSO, custom domains ✨ | ★★★★ | 💰💰 | 👥 Startups & product docs | ✨ Granular access + AI agent 🏆 |
ReadMe | MDX/React API ref, versioning, analytics ✨ | ★★★★ | 💰💰💰 | 👥 API teams & platforms | ✨ Interactive MDX + Dev Dashboard 🏆 |
Mintlify | Git-backed editor, API playground, AI ✨ | ★★★★ | 💰💰 | 👥 Dev-tools companies | ✨ Design-first docs & components 🏆 |
Redocly | OpenAPI renderer, Try-it console, CDN ✨ | ★★★★ | 💰💰💰 | 👥 API-heavy enterprises | ✨ Enterprise governance & scale 🏆 |
Document360 | WYSIWYG/Markdown, AI search, SSO ✨ | ★★★★ | 💰💰💰 | 👥 Support teams & enterprises | ✨ Migration, SOC2 readiness 🏆 |
Confluence (Cloud) | Page trees, templates, Jira apps ✨ | ★★★ | 💰💰 | 👥 Cross-team enterprise | ✨ Deep Jira ecosystem & governance 🏆 |
HelpDocs | AI drafts, templating, multilingual ✨ | ★★★★ | 💰💰 | 👥 Support/SaaS help centers | ✨ Quick setup + widget/multilang |
Slab | Clean editor, verification, analytics ✨ | ★★★★ | 💰 | 👥 Internal teams & SMEs | ✨ Verification & adoption focus |
Read the Docs | CI builds, versioning, previews ✨ | ★★★ | 💰 | 👥 OSS & engineering teams | ✨ Docs-as-code hosting & previews |
Docusaurus | MDX, i18n, plugins, themeable ✨ | ★★★★ | 💰 (dev cost) | 👥 Dev teams wanting control | ✨ Max control & extensibility 🏆 |
MkDocs | Markdown builds, plugins, deployable ✨ | ★★★ | 💰 | 👥 Markdown/Git-centric teams | ✨ Lightweight & fast builds |
Notion (docs/wiki) | Databases, publish, API, verification ✨ | ★★★★ | 💰 (bundled) | 👥 Non-technical teams & startups | ✨ Rapid adoption; pairs with Sotion for polish 🏆 |
Final Thoughts
Navigating the world of software documentation software reveals a clear truth: there is no single, perfect solution for every team. The ideal choice hinges entirely on your specific circumstances, including your team's size, technical proficiency, budget, and the nature of the documentation you need to create. From powerful, developer-centric tools that live alongside your code to user-friendly platforms designed for speed and simplicity, the options we've explored cater to a wide spectrum of needs.
The journey from messy, disorganized information to a clean, accessible knowledge base is a significant undertaking, but choosing the right foundation makes all the difference. Your decision is a strategic one that will impact developer onboarding, user adoption, and overall product success.
Key Takeaways and Decision-Making Framework
Reflecting on the dozen tools we've analyzed, a few core themes emerge. The most critical decision point often boils down to the "Docs-as-Code" philosophy versus a WYSIWYG editor approach.
- For Developer-First Workflows: If your documentation is deeply intertwined with your codebase and your team is comfortable with Markdown, Git, and command-line interfaces, then a Docs-as-Code solution is likely your best fit. Tools like Mintlify, Docusaurus, MkDocs, and Read the Docs offer unparalleled version control, automation, and integration with your existing development processes. They treat documentation as a first-class citizen of your software project.
- For Speed and Accessibility: If your priority is enabling non-technical team members to contribute easily, a platform with a rich graphical editor is essential. Confluence, Slab, Document360, and Notion excel here. They lower the barrier to entry, allowing marketing, support, and product teams to create and update content without needing to touch a line of code.
- For External, Public-Facing Docs: When your audience is your user base, presentation and discoverability are paramount. GitBook, ReadMe, and HelpDocs are specifically built for creating beautiful, searchable help centers and API references. They offer features like powerful search, user feedback mechanisms, and analytics that are crucial for customer-facing documentation.
Your Action Plan for Selecting a Tool
Feeling overwhelmed? Don't be. Follow these practical steps to narrow down your options and make a confident choice:
- Define Your Primary Use Case: Are you building an internal wiki, a public API reference, a user guide, or all of the above? Be specific. A tool great for one is often mediocre for another.
- Identify Your Core Contributors: Who will be writing and maintaining the documentation? Are they engineers, technical writers, or support specialists? Match the tool's interface to their skill set.
- Audit Your Existing Content: Where does your information live now? Is it in Google Docs, Confluence, Markdown files, or scattered across Notion pages? Consider the migration effort. Some tools offer robust importers, while others require a manual copy-paste effort.
- Run a Small-Scale Trial: Before committing, select your top two or three candidates and run a pilot project. Task a small group with creating a sample documentation site. This real-world test will reveal workflow friction and usability issues far better than any feature list.
- Consider Long-Term Scalability and Maintenance: Think about your company's growth. Will this tool scale with you? What is the maintenance overhead, especially for open-source solutions like Docusaurus or MkDocs? Who will be responsible for updates and security?
Finally, as you build out your documentation portal, remember that accessibility is not an afterthought. Ensuring your content is usable by people with disabilities is crucial for creating an inclusive product experience. As you design your site, it’s wise to incorporate key website accessibility best practices to ensure your documentation reaches the widest possible audience.
Choosing the right software documentation software is the first step toward building a culture of knowledge sharing. The investment you make today will pay dividends in faster onboarding, fewer support tickets, and a more empowered user base.
Ready to turn your existing Notion pages into a polished, professional documentation site in minutes? Sotion is the fastest way to build a secure, branded help center or knowledge base directly from your Notion workspace. Get custom domains, password protection, and a beautiful front-end without writing a single line of code. Try Sotion today and launch your documentation site instantly.
_circle.png)
Written by
Meet Bruce, the founder behind Sotion, and explore his vision on enhancing Notion Pages. Get a glimpse of the journey and the future roadmap of Sotion.