Questions,
answered.

How Novus thinks about analytics, code, and what it actually does once it’s connected.

• How is Novus different from traditional analytics tools?

  Traditional tools wait for you to tag things. Novus reads your codebase and instruments automatically. When your code changes, your analytics update. You don’t have to touch anything.

• What does Novus actually do with my codebase?

  Novus reads your code to understand the structure of your product — routes, flows, interactions, and how they connect. It uses that to instrument automatically and keep your analytics current.

  Your source code is never stored, shared, or used for model training. You connect the repos you choose, and you can revoke access at any time.

• What’s the relationship between Novus and Pendo?

  Novus is a separate product built by the Pendo team. It runs independently. For existing Pendo customers, nothing changes — Novus is for teams who want product understanding that keeps pace with how software is built today.

• What repos do you support?

  GitHub to start. Bitbucket, Azure DevOps, and GitLab are on the roadmap.

• Does Novus replace Pendo?

  Novus is an alternative to Pendo for a given application. Existing apps in Pendo continue to work as normal, and we continue to invest heavily in improving Pendo every day. New apps can be set up using either Novus or Pendo. If you leave Novus, the app can be set up in Pendo instead.

• Does Novus make changes to my product automatically?

  Never. Novus proposes changes only via pull requests. Engineers review and merge everything. There are no automatic merges, no production changes without approval, and no black-box automation without full visibility.

How your code is handled, where data flows, and what you’re responsible for.

• Do you train AI models on my code?

  No. Your codebase is never used for model training. Novus reads your code to understand structure — it doesn’t store or share it.

• How long does Novus retain my source code?

  It doesn’t. Code is handled ephemerally — Novus clones your repository to perform analysis and removes it once the operation completes. Novus does not retain a persistent copy of your source code.

• What AI is used to analyze my code?

  Novus uses Claude Code, operated by Pendo. Customers don't bring their own AI models. You control which repositories Novus can access — this is enforced through the permissions you grant the Novus GitHub app in GitHub itself. Novus will only actively monitor the repositories you explicitly add as apps.

• Where does behavioral data go?

  Instrumentation and behavioral data flow through standard Pendo infrastructure. If session replay is enabled, you’re responsible for ensuring appropriate user consent under applicable privacy laws.

• What are my compliance obligations?

  You’re responsible for ensuring your organization has obtained appropriate end-user notices and consents required under applicable privacy laws before sharing data with Pendo. This includes consents for behavioral tracking, session replay (if enabled), and metadata collection.

What participation looks like — requirements, support, pricing, and exit terms.

• What do I need to participate?

  You’ll need access to your application’s source code repository on GitHub, permission for Novus to clone it ephemerally and open pull requests, and one or more applications to connect. Multiple apps are supported.

  You’ll also need to confirm that your organization has obtained appropriate end-user notices and consents required under applicable privacy laws.

• Can I connect multiple apps or repos?

  Yes, multiple apps are supported in the Closed Beta. At launch, one repository per app is supported. Monorepo and multi-repo-per-app support will be introduced during the beta period.

• How does support work during the beta?

  Support runs through a single channel: novus@pendo.io. It’s monitored directly by the Novus product and engineering teams, so responses come straight from the people building the product. Self-serve documentation covers setup, configuration, and common workflows. There are no dedicated Slack channels or scheduled calls during the Closed Beta — this lets the team focus on building and on responding to every customer through a single channel.

• Is Novus free during the beta?

  Yes. Novus remains free throughout the Closed Beta. Pricing will be introduced later this summer, and beta participants will receive advance notice before any changes take effect.

• How will pricing work after the beta?

  Paid plans will be structured around usage — launches analyzed, UX reviews, and team size. We’ll publish pricing before the beta ends and give you time to decide which plan is right for you.

• Can I stop using Novus at any time?

  Yes. You can stop using Novus at any time. Ending your use does not include a guaranteed migration path to standard Pendo — reach out at novus@pendo.io if you’d like to discuss your options.