The Modern Billing Standard

How "Per Company File"
Billing Works

The core of the nXus model is that you pay for the data source, not the number of times you connect to it. Predictable, transparent, and built for scale.

Free

For prototypes, sandbox integrations, and early validation.

500 requests/hour

No card required while you validate your integration.

  • QuickBooks sample file support for dev and testing
  • Full API surface for building and validating flows
  • Move to paid when you need production throughput

Standard

For live company files that need predictable production access.

$250/year
$300/year2 months free in year one
  • Billed per company file connection
  • Annual billing includes 2 months free in year one
  • Ideal for production QuickBooks Desktop environments

Early Sign-Up Promo

Introductory pricing for early customers who want to lock in a lower annual rate.

Limited-time
$200/year
$300/year2 months free in year one
  • Promo pricing applies to annual billing only
  • Annual billing includes 2 months free in year one
  • Monthly billing remains $25 per company file

Per company file billing

Pricing is per connection, billed once per company file. If multiple connections point to the same QuickBooks file, that file is only billed once.

Testing connections

A QuickBooks sample file can be used for development and testing. Testing data may be cached for analysis and is not treated as secure storage, so sample data only.

Production connections

Production traffic currently runs as a pass-through. No production data persists on nXus servers and the server does not retain knowledge of that data after the request completes.

Architecture Details

One interface, one file, one bill

Stop maintaining brittle COM automation and paying per connector. nXus creates a unified translation layer that bills against the data source itself.

One File, One Bill

A single live QuickBooks company file counts as one paid connection.

Duplicate Links

If you have multiple integrations or apps connecting to the same underlying company file, you are still only billed once for that file.

Multiple Files

If you manage multiple different QuickBooks company files, each one requires its own separate billable connection.

Environment Details

Development

You should use QuickBooks sample files for testing. Data in this environment may be cached for analysis.

Production

Traffic is handled as a "pass-through." No production data is persisted or stored on nXus servers after a request is completed.

Management

All paid plans are activated via your dashboard, and you can manage invoices or cancellations through the integrated billing portal, but billing is done securely through Stripe.

All data transmission is encrypted via TLS 1.2+. Payment processing and subscription management handled securely through Stripe.

Ready to modernize your integration?

Start on the free tier to validate your integration with sample data. No commitment, no credit card required to begin.