Create a Product & Connect Sources

A Product in Sequa is a container for a complete software system. It’s the central workspace where you group all the knowledge sources for a single project, like a web application, a mobile app, or an internal tool.

Creating a product and connecting its sources is the most important step in setting up Sequa. This guide will walk you through the entire process.

Starting the Product Creation Wizard

You can create a product in two ways:

For New Organizations: After creating your organization, you will be automatically guided to create your first product.
For Existing Organizations: From your organization’s dashboard, click the “Create Product” or “New Product” button.

Both paths will launch the same setup wizard.

Step 1: Name Your Product

The first step is simple: give your product a clear, descriptive name. This is how you and your team will identify it within Sequa.

Good examples: Customer Web App, Billing API, Internal Admin Dashboard.

Step 2: Connect Code Repositories

This is the most critical step. Sequa builds its core understanding of what your system does and how it’s built by analyzing your code and its history. A product can (and often should) contain multiple repositories that work together.

You have several options for connecting your repositories:

GitHub (Recommended): The easiest method is to install the Sequa GitHub App. This will open a window allowing you to grant Sequa access and visually select all the repositories that belong to this product.
GitLab: You can connect repositories hosted on GitLab.
SSH: For any other Git-based provider (like Bitbucket or a self-hosted instance), you can provide access by adding an SSH key.

See the Integrations page for current availability and planned sources.

Step 3: Connect Other Data Sources (Optional)

To give Sequa a complete picture—including the “why” behind your code—you can connect other sources of knowledge. This is optional but highly recommended for the richest context.

Static Documentation: If you have existing docs in Confluence, connect them here.
Task & Project Management: Connecting to Jira or Linear allows Sequa to link code changes back to the specific tasks and requirements that prompted them.

See the Integrations page for current availability and planned sources.

Step 4: Indexing Begins

Once you click “Finish”, Sequa starts indexing all the sources you’ve connected. This is not a simple file scan; it’s a deep and comprehensive process where Sequa builds a connected knowledge graph of your code, its dependencies, and its full history.

To ensure the highest quality context, this initial indexing can take some time—from several minutes to an hour, depending on the size and history of your repositories.

You will receive an email notification as soon as the indexing is complete.

Next Steps

Once you receive the email notification, your product is ready. You can now begin exploring its knowledge:

Ask Sequa your first question.
Create a self-maintaining page to document a core concept.

Create a Product & Connect Sources

Creating a product and connecting its sources is the most important step in setting up Sequa. This guide will walk you through the entire process.

Starting the Product Creation Wizard

You can create a product in two ways:

For New Organizations: After creating your organization, you will be automatically guided to create your first product.
For Existing Organizations: From your organization’s dashboard, click the “Create Product” or “New Product” button.

Both paths will launch the same setup wizard.

Step 1: Name Your Product

The first step is simple: give your product a clear, descriptive name. This is how you and your team will identify it within Sequa.

Good examples: Customer Web App, Billing API, Internal Admin Dashboard.

Step 2: Connect Code Repositories

You have several options for connecting your repositories:

GitHub (Recommended): The easiest method is to install the Sequa GitHub App. This will open a window allowing you to grant Sequa access and visually select all the repositories that belong to this product.
GitLab: You can connect repositories hosted on GitLab.
SSH: For any other Git-based provider (like Bitbucket or a self-hosted instance), you can provide access by adding an SSH key.

See the Integrations page for current availability and planned sources.

Step 3: Connect Other Data Sources (Optional)

To give Sequa a complete picture—including the “why” behind your code—you can connect other sources of knowledge. This is optional but highly recommended for the richest context.

Static Documentation: If you have existing docs in Confluence, connect them here.
Task & Project Management: Connecting to Jira or Linear allows Sequa to link code changes back to the specific tasks and requirements that prompted them.

See the Integrations page for current availability and planned sources.

Step 4: Indexing Begins

To ensure the highest quality context, this initial indexing can take some time—from several minutes to an hour, depending on the size and history of your repositories.

You will receive an email notification as soon as the indexing is complete.

Next Steps

Once you receive the email notification, your product is ready. You can now begin exploring its knowledge:

Ask Sequa your first question.
Create a self-maintaining page to document a core concept.