Frequently Asked Questions

QuantalQ Doc

Answers to your questions about the usage of the Documentation Application

Features & Integrations

Our documentations are structured according to the ISO/IEC 26515:2018 standard (Developing information for users in an agile environment), ensuring clarity, consistency, and ease of use. It is delivered as a well-organized, easy-to-navigate PDF designed to support both technical and non-technical readers with relevant information.

To make complex processes easy to understand, we include helpful PlantUML diagrams such as system architecture overviews, process flows, data relationship models, and sequence diagrams. Following ISO/IEC 26515:2018, we focus on task-oriented content, clear visual guidance, and structured information that supports all readers throughout their entire usage journey.

To make complex processes easy to understand, we include helpful PlantUML diagrams such as system architecture overviews, process flows, data relationship models, and sequence diagrams. Following ISO/IEC 26515:2018, we focus on task-oriented content, clear visual guidance, and structured information that supports you throughout your entire usage journey.

We support all GIT repositories, as long as they are accessible via the internet and can be connected using an API token. This includes popular platforms like GitHub, GitLab, Bitbucket, and others that provide standard GIT and API access.

Accounts & Login

At the moment, the only difference is that with an Organization Account, you can add your company details, which is required for contractual purposes only. In the future, Organization Accounts will also allow you to invite and manage other employees from your company, so that multiple team members can create and run projects under the same Organization Account.

We take security seriously. In today’s world, using just a username and password is no longer secure enough. The information you share with us deserves the best possible protection. That’s why we require two-factor authentication – to add an extra layer of security and keep your data safe from unauthorized access.

Not yet but we are already planning to introduce Passkey login as an additional option in the future, so you’ll be able to log in even more securely and conveniently.

Documentation Project

A project defines which product repository should be automatically documented.

You select a repository and a branch as input. The result is always up-to-date, automatically generated documentation.

A project can run manually with a single click or automatically*, for example on a schedule or triggered by events. In both cases, the documentation is created fully automatically, with no manual work required.

* comming soon

At the moment, we do not offer an editor function. Until this service becomes available, the QuantalQ team can make adjustments upon request, which will also be taken into account in future versions of the documentation.

To connect your code repository, you’ll need to create a personal API token (also called a personal access token) from your Git provider. This token allows secure access without using your username and password.

Here’s where you can create your API token depending on your provider:

Once generated, simply copy the token and paste it into the required field on the Projcet creation page in teh QuantalQ Doc Customer Portal. Make sure to store your token securely, as it grants direct access to your repositories.

Pricing & Payment

We do not offer a freemium plan. However, we provide a flexible pay-as-you-go option that allows you to test our QuantalQ Doc at a low entry cost – without the need to start with a full subscription. While there is a small base fee involved, you remain fully in control of your usage and costs. 

We currently do not offer online payment. Instead, we issue invoices, which you can settle via bank transfer or according to the agreed payment terms.

For personalized advice or a tailored offer, you can contact our sales team at any time. 
sales@quantalq.com

Scroll to Top