Frequently Asked Questions

Everything you need to know about Theneo’s AI-native docs & developer portals

What is Theneo and who is it for?

Theneo is an AI-powered API documentation platform that automatically generates, maintains, and publishes interactive developer docs. It's built for product teams, engineering teams, and developer relations professionals who need to keep API documentation accurate, beautiful, and always up-to-date without manual work.

What problems does Theneo solve?

Theneo eliminates outdated API docs, reduces documentation maintenance time by up to 80%, and creates interactive references that developers actually want to use. Teams switching to Theneo typically see faster developer onboarding, fewer support tickets about API usage, and more consistent documentation across all their APIs.

How is Theneo different from traditional documentation tools?

Unlike static doc generators or wikis, Theneo connects directly to your codebase and automatically detects API changes, suggests updates, and keeps examples current. Our AI understands your API structure and generates human-quality descriptions, while the interactive "Try-it" feature lets developers test endpoints without leaving the docs.

How long does it take to get started with Theneo?

Most teams publish their first auto-generated documentation within 30 minutes. Enterprise implementations with custom branding and SSO typically take 1-2 weeks including design review and security approval.

What types of APIs and formats does Theneo support?

Theneo supports all major API documentation formats including OpenAPI/Swagger (2.0 & 3.x), Postman Collections, GraphQL (SDL & introspection), gRPC (proto files), SOAP/WSDL, and AsyncAPI. You can import specifications in YAML, JSON, or Markdown formats.
Theneo also lets you combine auto-generated API reference documentation with hand-written guides and tutorials in Markdown or MDX - perfect for creating complete developer documentation portals with both technical reference and getting-started content.

Do we need to change our development workflow?

No. Theneo fits into your existing workflow through GitHub/GitLab integration, CI/CD pipelines, or our CLI. You choose whether docs update automatically on every commit, require PR approval, or publish on a schedule.

Can non-technical team members contribute to API documentation?

Yes. Product managers and technical writers can edit descriptions, add guides, and manage content through our visual editor - no code required. Technical teams handle the API schema while others perfect the narrative.

Can we keep our documentation private?

Yes. Theneo gives you complete control over documentation access at multiple levels:

Documentation-level privacy: Choose to keep your entire documentation portal private, public, or a mix of both.
Endpoint-level permissions: Control access for individual API endpoints - make some public while keeping sensitive endpoints private, or restrict specific endpoints to certain user groups.
External user authentication: For public-facing APIs that require access control, enable user registration and authentication flows so external developers can sign up and access your private documentation with approved accounts.
This flexibility means you can have public documentation for your external API while keeping internal endpoints, beta features, or enterprise-only APIs completely private - all within the same documentation portal.

How interactive is the API reference? (examples, auth, “try it”)

Theneo's interactive API documentation includes live "Try It" functionality that lets developers test API endpoints directly in the browser. Features include:


Live API testing: Developers can make real API calls with their own API keys or OAuth authentication


Environment switching: Toggle between production, staging, and development base URLs to test against different environments.


Auto-generated code examples: Sample requests and responses are automatically generated from your API schema in multiple programming languages (JavaScript, Python, cURL, Java, and more).


Customizable examples: Use auto-generated samples, add your own curated examples, or combine both - tailored per language and use case.


This means developers can authenticate, explore, and integrate your API without leaving your documentation.

How far can we customize and white-label our API documentation?

Theneo offers extensive customization from simple branding to complete white-label solutions. It gives you full control over CSS/JavaScript, custom typography, page layouts, navigation sidebars, landing pages, and completely bespoke API reference UI design. Remove all Theneo branding for a seamless experience. Your documentation can look and feel like a native part of your website or developer portal.

Can we use our own custom domains and environments?

Yes. Theneo supports custom domains with SSL certificates (e.g., docs.company.com or developers.yourapp.com) so your API documentation lives on your branded domain.


Multiple environments: Create separate documentation instances for production, staging, and development environments, each with environment-specific variables, API keys, and base URLs.


Flexible hosting: Choose between public documentation, private internal docs, or mixed visibility - all on your own domain with full SSL security.

How powerful is search?

AI search + semantic Q&A across references and guides, typo-tolerant and synonym-aware, with filters/facets. Enterprise can search across multiple projects/workspaces.

Can Theneo automate changelogs and release notes?

Yes. Theneo automatically detects changes in your API specifications and generates changelogs and release notes without manual tracking:
When you update your OpenAPI spec, Postman collection, or code, Theneo identifies what changed (new endpoints, modified parameters, deprecated fields, etc.).

This keeps your API documentation and changelog always in sync with your actual API, eliminating the manual work of tracking and documenting every change.

How do we control access to our API documentation? (SSO, RBAC, private/public)

Theneo provides enterprise-grade access control with multiple authentication and authorization options:


Role-based access control (RBAC): Assign different permission levels to team members and external users - admins, editors, viewers, or custom roles with granular permissions.
Single Sign-On (SSO): Integrate with your existing identity provider via SAML, OIDC, or JWT. Supported providers include Okta, Azure AD, Google Workspace, Auth0, and other enterprise SSO solutions.


Access management features:

- Domain allow-lists
- Private sections within public documentation
- Approval queues for user registration requests
- Comprehensive audit logs tracking all access and changes

Perfect for enterprises requiring secure, compliant documentation access aligned with corporate identity management.

What about hosting options, data residency, and certifications?

Theneo offers flexible, secure hosting with enterprise compliance:


Cloud hosting: Hosted on AWS (U.S. by default) with enterprise-grade security including encryption in transit (TLS) and at rest (AES-256). Automated backups and business continuity/disaster recovery (BCP/DR) protocols ensure data protection.


Regional data residency: Enterprise customers can request regional hosting in the EU, Asia-Pacific, or other regions to meet data sovereignty requirements.


Self-hosting options: For maximum control, Enterprise plans support private cloud or on-premises deployment with AI features disabled (BYO-AI) or fully enabled.


Compliance certifications: ISO 27001 (information security), ISO 9001 (quality management), SOC 2 Type II, and GDPR compliant.


Your documentation infrastructure meets the same security standards as your production systems.

How do you handle performance and traffic spikes?

Global CDN and caching; assets and pages are optimized for fast TTFB and LCP. Proven with large, high-traffic public portals and very large specs/content sets.

Does Theneo support localization?

Yes. Theneo supports multi-language API documentation to serve global developer audiences. You may create localized versions combining both for quality and speed.

What does onboarding and support look like? What are the SLAs?

Theneo provides comprehensive onboarding including migration assistance from your current documentation tool, email support, and access to our documentation knowledge base.
It also includes:

- Dedicated account manager assigned to your team

- Hands-on design and customization services

- Private Slack or Teams channel for direct communication

- Weekly check-ins during onboarding

- Staging environments for testing before production deployment

Service Level Agreements (SLAs): Uptime and support response SLAs are defined. Enterprise customers receive priority support with guaranteed response times and 99.9% uptime commitments.
Our goal is to get your documentation live as soon as possible with ongoing support as your needs evolve.

All of this to increase
API usage & adoption 3x times