About Novix

Novix is an agent that starts where a bug actually starts: a person reporting it. A customer writes into your help desk, a colleague says something in Slack, or your monitoring sees an error before anybody files anything. Novix reads the report, works out the root cause against your codebase, drafts a fix, runs your own build and tests against it in a throwaway sandbox, and opens a pull request. Your engineers review a change, not a ticket.

Why it starts at the report

Most tools in this category start from an alert, or from an issue an engineer has already written up. That is the easy half. The expensive half is everything in front of it: reading what a customer said, working out whether it is a defect at all, finding who it affects, and turning it into something an engineer can act on.

That is why Novix reaches into 37 connectors rather than one. People report bugs wherever they already are, so Novix goes there instead of asking anybody to come to it. On 17 of them you can summon Novix and approve the fix without opening Novix at all, and the pull request lands in the repository your team already reviews in.

Who is asking is part of the input. Connect a CRM, or save your own read-only queries against your own database, and the account behind a report can raise its priority, so a paying customer is not ranked below whichever exception happened to fire most often. Novix never writes those queries and never writes to your database.

What Novix will not do

The boundary is the product. A person decides, and there is no setting that changes it.

• Novix never merges its own pull request. A person merges it, and merging is the approval.
• Every drafted fix is reviewed twice before you see it, once for security holes it introduces and once for safety, and then built and tested in an isolated container.
• Novix never writes to your database, and it never writes the queries it runs against one.
• A rejected draft is never billed. Only an approved fix is, and only when the run used Novix’s inference account rather than your own.
• Novix is not a replacement for your issue tracker. It works inside the one you have.

The company

Novix is early and founder-led. The product is live, it runs on real customer workspaces, and it is still pre-launch in the sense that matters to a buyer: the legal documents say so on their face, and the pricing, the trial and the cancellation terms are published rather than negotiated. If you want to see it work on something real, you can book time with the founder rather than a sales team.

The sandbox that builds and tests every candidate fix runs on E2B, and Novix is in E2B for Startups. That is sponsored sandbox credit, not an investment.

How it is built

Novix is built on Claude and tuned for it. On the Pro plan you can point it at your own inference account instead, which changes whose account pays rather than which model does the work. That is a cost, compliance and procurement choice, and it is never a claim that Novix runs equally well on any model.

What Novix stores, for how long, and who can read it is written out in the privacy policy. How your source code and credentials are handled is in the security page, and every third party that touches customer data is listed under subprocessors.

Talk to us

One address reaches a person: support@getnovix.ai. Support, sales, privacy requests and security reports all land there. The contact page says what to expect from each.