OpenSalesTax
github.com
- Free plan
- Open source
- macOS
- Linux
- Web
- API
- Self-hosted
What OpenSalesTax is
OpenSalesTax is a free, self-hostable API for calculating sales tax on US transactions. Its per-state modules cover 52 jurisdictions, while each published data dump includes all 48 jurisdictions that impose sales tax. The API calculates tax for line items and can return a breakdown by state, county, city, or district. Documented item categories include general goods, clothing, groceries, prescription drugs, prepared food, and digital goods. The project uses Streamlined Sales Tax files and state Department of Revenue publications rather than paid tax data feeds. You can install it from source or run it with Docker. PostgreSQL is the default database, with MariaDB available as an optional extra. Access defaults to open with per-IP rate limiting; an API-key mode adds per-key limits and usage tracking. The project documents how to fetch and load newer data. It identifies incomplete sub-state tax stacking for Colorado home-rule cities and Louisiana parish-level collectors. OpenSalesTax is pre-1.0, and its public users registry lists no self-hosters or integrators.
Who it suits
OpenSalesTax may suit developers or organizations that want to host a US sales-tax API and work with its data-loading process. It is pre-1.0, and users should verify calculations with the relevant state Department of Revenue before remitting.
Good to know, and what to watch
- Free and self-hostable under Apache 2.0.
- Calculates tax for line items with jurisdiction breakdowns.
- Supports PostgreSQL and optional MariaDB.
- API-key mode provides per-key limits and usage tracking.
- Pre-1.0 project with no listed self-hosters or integrators.
- Tax stacking is incomplete for some Colorado and Louisiana areas.
- Docker runtime image lacks the psql client.
- Calculations are not legal or tax advice.
Plans
Every plan and priceFree / open source
Free self-hosted engine
Free plan
Getting started
- Open the OpenSalesTax GitHub website
- Install the engine from source or run it with Docker
- Provide PostgreSQL, or add the optional MariaDB support
- Load a published data dump or fetch newer source data
- Choose open access or configure API-key authentication with X-API-Key
Limits to check
The project identifies incomplete sub-state tax stacking for Colorado home-rule cities and Louisiana parish-level collectors. In Docker, restoring data fails unless the psql client is added or the source-install route is used.
The verdict
OpenSalesTax offers a no-cost, self-hosted route to sales-tax calculations using public data. Its pre-1.0 status, identified coverage gaps, and data-restore caveat matter when deciding whether it fits a production workflow.
Questions people ask
What does OpenSalesTax cost?
The Free / open source plan costs nothing and uses the Apache 2.0 license.
Which platforms does it support?
It is offered as an API and self-hosted software. You can install it from source or run it with Docker.
Which database does it use?
PostgreSQL is the default database, with MariaDB available as an optional extra.
How is API access controlled?
Access defaults to open access with per-IP rate limiting. API-key mode requires an X-API-Key header and supports per-key limits and usage tracking.
What data does it use?
It uses Streamlined Sales Tax files and state Department of Revenue publications, not paid tax data feeds.
What the maker publishes
- Adoption status
- The public users registry says there are no listed self-hosters or integrators yet and that OpenSalesTax is pre-1.0. source
- Advice disclaimer
- The project says its calculations are not legal or tax advice and advises verifying results with the relevant state Department of Revenue before remitting. source
- Advice disclaimer
- The project describes its output as calculation only, not legal or tax advice, and tells users to verify results with their state revenue department. source
- API access
- Authentication defaults to open access with per-IP rate limiting, while an API-key mode requires an X-API-Key header and supports per-key rate limits and usage tracking. source
- API endpoints
- The documented API exposes health, jurisdiction coverage, ZIP-based rates, and POST tax calculations under version 1 routes. source
- Calculations
- The API calculates tax for line items and can return a breakdown by state, county, city, or district jurisdiction. source
- Contributions
- Contributors must sign commits using the Developer Certificate of Origin process. source
- Coverage
- The project says it has modules for 52 jurisdictions, with all 48 sales-taxing jurisdictions loaded into each published data dump. source
- Coverage limitation
- Colorado home-rule cities and Louisiana parish-level collectors are not fully represented, so sub-state stacking is incomplete there. source
- Database support
- MariaDB is available through an optional installation extra, but the bundled release dump is PostgreSQL COPY format. source
- Data refresh
- Release data dumps are pinned to the SST quarterly file current at release time, and the project documents fetching and loading newer source data. source
- Data refresh
- Operators can bypass the bundled dump and fetch and load newer state data directly from upstream sources. source
- Data-release limitation
- Release dumps before v0.59.0 omitted 23 taxing states and require restoration from a corrected asset. source
- Data sources
- The project uses Streamlined Sales Tax files and state Department of Revenue publications, and says it does not ingest paid tax data feeds. source
- Deployment
- Users can install from source with Poetry and PostgreSQL or run the stack with Docker Compose. source
- Docker limitation
- The README says the runtime image lacks the psql client, so data restore fails in the container unless the package is added or the source-install path is used. source
- Docker limitation
- The published runtime image lacks the psql client, so the documented data-restore command fails in the container until that package is added. source
- Holiday rules
- The engine includes holiday-aware calculations, illustrated by a Texas clothing exemption example. source
- Hosting
- The engine can be installed from source or run with Docker and requires PostgreSQL by default; MariaDB support is available as an optional extra. source
- Independent limitation
- WiserReview says users must host and update the engine, handle remittance themselves, and that marketplace and multi-vendor allocation are not covered. source
- Independent pricing assessment
- WiserReview lists the engine and WooCommerce plugin at $0 software cost, with hosting and maintenance left to the user. source
- Item categories
- Documented categories include general, clothing, groceries, prescription drugs, prepared food, and digital goods. source
- Jurisdiction detail
- Calculation responses break tax into state, county, city, and district jurisdictions so totals can be reconciled. source
- License
- The engine is released under the Apache License 2.0. source
Checked against the maker's pages on 15 Oct 2026.