LEGAL

Tabsdata Software License Agreement

Version 1.7.0-2026-03-01-001

Plain-Language Summary

This summary explains the license in plain English. It is provided to help you understand the intent quickly. It is not a substitute for the actual license terms, which follow in the next section and are the legally binding document.

What Tabsdata is and how it is distributed

Tabsdata is a data integration platform. It moves data between systems, tracks every version of every dataset, and gives you a full history of what changed and when. It is distributed as Python packages via PyPI — you install it with pip — and what you get is the complete product. There is no cut-down free version and no premium upgrade. Everyone gets the same software.

Most of the code is open source under the Apache 2.0 license, published on GitHub. The remainder is proprietary and distributed in binary form as part of the same package. Tabsdata may open-source additional portions over time — the exact split is not fixed and may shift as the product evolves. This Agreement governs your use of the proprietary components and the integrated distribution. The open-source components remain governed by Apache 2.0, and are available directly from our GitHub repository. Nothing in this Agreement changes that.

The software is self-contained and runs entirely within your own infrastructure. It does not transmit usage data, telemetry, or any other information back to Tabsdata, Inc.

It is free to use

You do not need to pay anything to use Tabsdata. There is no per-seat fee, no per-core fee, no usage meter, and no time limit. Tabsdata, Inc. earns revenue only from optional paid support contracts. The software itself costs nothing.

What you can do

You are free to:

  • Use it internally for any purpose. Build dataflows, move data, run it on your servers, integrate it into your data platform. No restrictions on scale, volume, users, or number of dataflows.
  • Build an internal data platform on top of it. If you want to offer a shared data service to your own teams, business units, or subsidiaries — all within your own organisation — that is fully permitted.
  • Use it as a developer. If you are an individual developer building, testing, or evaluating Tabsdata — whether on your own or on behalf of your employer — you are covered at no charge.
  • Use the open-source components however Apache 2.0 allows. Fork it, modify it, and embed it in other projects. The open-source license governs those rights and this Agreement does not restrict them. If you would like to contribute back to the open-source project, please contact Tabsdata, Inc. — Tabsdata reserves the right to accept or decline contributions at its discretion.

What you cannot do

There are three things this license does not permit:

  • Resell it or build a commercial service on top of it for third parties. If the core of what you are selling to external customers is Tabsdata's functionality — whether packaged as a product, a hosted service, or a managed offering — that requires a separate commercial arrangement with Tabsdata, Inc.
  • Embed the proprietary components in a product you sell to others without telling us. If you want to ship a product to external customers that bundles the proprietary part of Tabsdata, you need to disclose that and get written consent first. Embedding the open-source components is fine under Apache 2.0 without any such requirement.
  • Reverse-engineer or copy the proprietary components. The proprietary components are protected by copyright and patents. You cannot decompile, copy, or build a derivative of the proprietary components. The open-source components are a different story — that code is openly available and you can do whatever Apache 2.0 permits.

Real-world examples

See Annex A at the end of this document for a full table of common scenarios with concrete examples of what is and is not permitted under this license.

Support

The software comes with no formal support obligation. If you want guaranteed response times, SLAs, and direct access to the engineering team, Tabsdata, Inc. offers paid support contracts. Those are entirely optional and governed by a separate agreement.

Confidentiality

The binary you download is not treated as confidential — it is distributed publicly. What is confidential is narrower: the source code of the proprietary components (not publicly available), any non-public technical documentation shared with you privately, and any product roadmap information shared during a commercial conversation. These should be treated with care.

One last thing

This plain-language summary is our attempt to be straightforward about what the license means. If there is ever a conflict between this summary and the actual license text that follows, the license text controls. If anything is unclear, or if you have a use case you are unsure about, you are welcome to reach out to Tabsdata, Inc. directly.

Preamble

This Tabsdata Software License Agreement (this "Agreement") governs the use of the Tabsdata data integration software and all related components, documentation, and updates distributed by Tabsdata, Inc. ("Licensor").

Tabsdata is distributed as one or more Python packages via PyPI, installable via pip, which together deliver the complete Software across both open-source and proprietary components. The Licensor offers the Software free of charge for internal use and monetizes exclusively through support contracts. The Software is distributed as a single unified package — the same distribution is available to all users. There is no feature-limited free tier and no separate paid edition.

This Agreement replaces any prior license agreement governing the Software, including any previous Master Services Agreement. If Licensee has executed a separate commercial support agreement with Licensor, the terms of that agreement supplement and, where they conflict with this Agreement, supersede this Agreement with respect to support and service-level obligations only.

1. Definitions

As used in this Agreement:

  • "Software" means the Tabsdata data integration platform in binary form, including all open-source and closed-source components distributed as part of the unified package, the Python SDK, connectors, documentation, and any updates, maintenance releases, or successor versions made available by Licensor.
  • "Open-Source Components" means those portions of the Software that Licensor has made available under an open-source license (currently the Apache License, Version 2.0) at https://github.com/tabsdata/tabsdata. The applicable open-source license terms govern use of those components independently.
  • "Proprietary Components" means those portions of the Software that are not Open-Source Components, including but not limited to the edition identity and distribution integrity layer, AI agent service integration, embedded web user interface, and advanced transaction granularity logic, which are protected by copyright and one or more patents filed by Licensor.
  • "Licensee" means the specific legal entity (including, where applicable, an individual acting in their personal capacity) that installs, accesses, or uses the Software, or on whose behalf the Software is installed, accessed, or used. Where a corporate group consists of multiple distinct legal entities, each such entity is a separate Licensee and the rights granted under this Agreement are not transferable across legal entities except as expressly permitted under the definition of Permitted Internal Platform and the Affiliate provisions herein.
  • "Affiliate" means any entity that directly or indirectly controls, is controlled by, or is under common control with a party, where "control" means ownership of more than fifty percent (50%) of the outstanding voting securities or equivalent interests.
  • "Internal Purposes" means Licensee's own internal business operations, data integration workflows, and data platform needs, whether performed directly by Licensee's personnel or by contractors operating exclusively on Licensee's behalf for Licensee's benefit. Internal Purposes expressly include operating a shared internal data platform that serves Licensee's business units, subsidiaries, or Affiliates. Internal Purposes do not include providing services, access, or functionality to third parties outside of Licensee and its Affiliates.
  • "Permitted Internal Platform" means a data integration or data-as-a-service platform built by Licensee using the Software that (a) serves only Licensee and its Affiliates, (b) is not made accessible to external third parties, and (c) is not offered as a service for compensation outside of Licensee's corporate group.
  • "Commercial Support Agreement" means a separate written agreement between Licensee and Licensor for support, maintenance, or professional services relating to the Software.

2. Grant of License

2.1 License Grant

Subject to the terms and conditions of this Agreement, Licensor grants to Licensee a non-exclusive, non-transferable, worldwide, royalty-free license to:

  • install and run the Software on systems owned, leased, or operated by or for Licensee;
  • use the Software for Internal Purposes, without restriction on the number of users, dataflows, datasets, cores, or volume of data processed;
  • build, operate, and maintain a Permitted Internal Platform using the Software as the underlying data integration engine;
  • access and use the Open-Source Components in accordance with the Apache License, Version 2.0, independently of this Agreement.

2.2 No Charge for Internal Use

The license granted in Section 2.1 is provided at no charge. Licensor monetizes the Software exclusively through Commercial Support Agreements. There is no usage fee, subscription fee, seat fee, or core fee for internal use.

2.3 Developer License

Individual developers — whether employed by, contracted by, or acting as agents of Licensee — may use the Software for development, testing, and integration activities under the same terms as Section 2.1. Such use is permitted at no charge and is not conditioned on a Commercial Support Agreement. Developer use on behalf of an organization binds that organization to this Agreement.

2.4 Open-Source Components

Nothing in this Agreement limits Licensee's rights under the Apache License, Version 2.0 with respect to the Open-Source Components. Where Licensee's use involves only Open-Source Components, the terms of the Apache License, Version 2.0 govern exclusively. This Agreement applies to the Proprietary Components and to Licensee's use of the Software as a complete integrated package.

3. Restrictions

3.1 Prohibited Uses

Licensee shall not, and shall not permit or enable any third party to:

  1. provide access to, distribute, sell, sublicense, or resell the Software, or offer any service primarily derived from the Software (meaning any service where the Software constitutes the primary functional engine of such service), to external third parties as a standalone product or service;
  2. use the Software to provide a hosted, managed, or software-as-a-service offering of data integration, dataflow orchestration, or data movement capabilities to external third parties, whether for compensation or otherwise;
  3. embed or bundle the Proprietary Components in a product or service offered to third parties without prior written disclosure to, and consent from, Licensor. For the avoidance of doubt, this restriction does not apply to the Open-Source Components, which may be used, embedded, and distributed in accordance with the Apache License, Version 2.0 without requiring disclosure to or consent from Licensor;
  4. attempt to reverse engineer, decompile, disassemble, or otherwise derive the source code of the Proprietary Components, except to the extent expressly required by applicable law (and then only with prior written notice to Licensor). For the avoidance of doubt, this restriction does not apply to the Open-Source Components, which are freely available under the Apache License, Version 2.0, and may be inspected, modified, and used in accordance with that license;
  5. modify, create derivative works of, or copy the Proprietary Components. This restriction applies solely to the Proprietary Components and does not limit Licensee's rights to modify, fork, or create derivative works of the Open-Source Components under the terms of the Apache License, Version 2.0;
  6. remove, alter, or obscure any copyright, patent, trademark, or other proprietary notices in or on the Software;
  7. circumvent or disable any license enforcement, feature-gating, or edition-identification mechanisms in the Software.

3.2 Clarification — Permitted Internal Platform

For the avoidance of doubt, the following uses are expressly permitted under Section 2.1 and do not constitute violations of Section 3.1:

  • Building and operating a shared internal data platform that ingests, transforms, and serves data to multiple business units, teams, or internal applications within Licensee's corporate group;
  • Offering Tabsdata-powered data movement as an internal shared service to Licensee's employees, contractors working exclusively for Licensee, and Affiliates;
  • Charging internal cost allocations or chargebacks for compute, storage, or support costs associated with operating the Permitted Internal Platform, provided such charges do not constitute resale of the Software.

4. Proprietary Rights and IP

4.1 Ownership

As between the parties, Licensor retains all right, title, and interest in and to the Software, including all Proprietary Components, all patents (whether filed or pending), copyrights, trademarks, trade secrets, and other intellectual property rights embodied therein. This Agreement does not transfer any ownership interest in the Software to Licensee. Licensee's rights are limited to those expressly granted in Section 2.

4.2 Patent Notice

To the extent the Proprietary Components are covered by one or more patents filed by Licensor, no license under those patents is granted except as necessary to use the Proprietary Components as permitted under Section 2. This Section 4.2 does not limit or supersede any patent license granted to Licensee under the Apache License, Version 2.0 with respect to the Open-Source Components; those patent rights are governed exclusively by the terms of that license.

4.3 Open-Source Components — No Restriction

Licensor's ownership of the Proprietary Components does not restrict Licensee's rights in the Open-Source Components. The Open-Source Components are separately licensed under the Apache License, Version 2.0, and Licensee may exercise those rights independently.

4.4 Feedback

If Licensee provides Licensor with any suggestions, enhancement requests, or feedback regarding the Software ("Feedback"), Licensee hereby grants Licensor a perpetual, irrevocable, royalty-free, worldwide license to use, reproduce, disclose, and incorporate such Feedback into the Software and other Licensor products without restriction or compensation to Licensee.

5. Disclaimer of Warranties

THE SOFTWARE IS PROVIDED "AS IS" AND "AS AVAILABLE" WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, LICENSOR DISCLAIMS ALL WARRANTIES, INCLUDING BUT NOT LIMITED TO IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. LICENSOR DOES NOT WARRANT THAT THE SOFTWARE WILL BE ERROR-FREE, UNINTERRUPTED, OR FREE OF SECURITY VULNERABILITIES.

WHERE APPLICABLE LAW DOES NOT PERMIT THE FULL EXCLUSION OF IMPLIED WARRANTIES, LICENSOR'S WARRANTIES ARE LIMITED TO THE MINIMUM WARRANTY REQUIRED BY LAW.

5.2 AI Agent Disclaimer

The Software includes an AI-powered agent ("Tabby") that integrates with third-party service providers (e.g., OpenAI) via a Licensee-provided API key. Licensee acknowledges and agrees that:

  • any dataflows, scripts, or configurations generated by Tabby are suggestions only and must be reviewed and tested by Licensee before execution in any environment;
  • Licensor is not responsible for any errors, data loss, or system downtime resulting from the execution of AI-generated content; and
  • Licensee is solely responsible for compliance with the terms of service and any costs associated with the third-party AI provider.

6. Limitation of Liability

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW:

  • IN NO EVENT SHALL LICENSOR BE LIABLE FOR ANY INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, CONSEQUENTIAL, OR PUNITIVE DAMAGES, INCLUDING LOSS OF PROFITS, LOSS OF DATA, BUSINESS INTERRUPTION, OR COST OF SUBSTITUTE GOODS OR SERVICES, HOWEVER CAUSED AND UNDER ANY THEORY OF LIABILITY, EVEN IF LICENSOR HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
  • LICENSOR'S TOTAL CUMULATIVE LIABILITY TO LICENSEE FOR ANY AND ALL CLAIMS ARISING OUT OF OR RELATED TO THIS AGREEMENT OR THE SOFTWARE SHALL BE LIMITED AS FOLLOWS: (A) FOR LICENSEES WHO DO NOT HOLD A CURRENT COMMERCIAL SUPPORT AGREEMENT: THE GREATER OF ONE HUNDRED UNITED STATES DOLLARS (USD $100) OR THE AMOUNTS PAID BY LICENSEE TO LICENSOR IN THE TWELVE (12) MONTHS PRECEDING THE CLAIM; (B) FOR LICENSEES HOLDING A CURRENT COMMERCIAL SUPPORT AGREEMENT: THE AMOUNT EXPRESSLY SET FORTH AS A LIABILITY CAP IN THAT AGREEMENT, OR IF NO AMOUNT IS EXPRESSLY SET FORTH, THE FEES PAID BY LICENSEE UNDER THAT AGREEMENT IN THE TWELVE (12) MONTHS PRECEDING THE CLAIM. THESE TWO CASES ARE MUTUALLY EXCLUSIVE; A LICENSEE WITH A CURRENT COMMERCIAL SUPPORT AGREEMENT IS GOVERNED SOLELY BY CLAUSE (B).

The foregoing limitations apply regardless of whether any remedy fails of its essential purpose.

7. Indemnification

Licensee shall indemnify, defend, and hold harmless Licensor and its officers, directors, employees, and agents from and against any claims, damages, losses, liabilities, costs, and expenses (including reasonable attorneys' fees) arising out of or related to: (a) Licensee's use of the Software, or incorporation of the Software into any product or service, in violation of this Agreement; or (b) Licensee's use of the Software to process data in violation of applicable law.

8. Term and Termination

8.1 Term

This Agreement is effective upon Licensee's first installation or use of the Software and continues until terminated as set forth herein.

8.2 Termination for Breach

Licensor may terminate this Agreement immediately upon written notice if: (a) Licensee materially breaches any provision of Section 3 (Restrictions) or Section 4 (Proprietary Rights and IP) and, where such breach is capable of cure, fails to cure it within thirty (30) days after receiving written notice of the breach; (b) Licensee commits any unauthorized use, reproduction, or distribution of the Proprietary Components or otherwise infringes Licensor's intellectual property rights with respect to the Proprietary Components. Termination under this clause (b) shall not affect Licensee's independent rights under the Apache License, Version 2.0 with respect to the Open-Source Components, which survive any termination of this Agreement; or (c) Licensee becomes insolvent, makes a general assignment for the benefit of creditors, or becomes subject to bankruptcy, receivership, or similar proceedings that are not dismissed within sixty (60) days.

8.3 Effect of Termination

Upon termination of this Agreement: (a) all licenses granted herein immediately cease; (b) Licensee shall promptly cease all use of the Software and destroy or return all copies of the Proprietary Components in Licensee's possession or control; and (c) Sections 1, 4, 5, 6, 7, 8.3, 9, and 10 shall survive termination.

Termination of this Agreement does not affect Developer License rights previously exercised in good faith before the date of termination, provided such use was in compliance with this Agreement.

9. Confidentiality

Licensee acknowledges that certain non-public information of Licensor constitutes confidential information ("Confidential Information"). For purposes of this Agreement, Confidential Information means: (a) the source code of the Proprietary Components; (b) non-public technical documentation, architecture materials, or design specifications relating to the Proprietary Components that are provided to Licensee outside of public channels; and (c) non-public product roadmaps and plans disclosed by Licensor to Licensee in connection with a commercial engagement. Confidential Information does not include the Software in binary form as distributed to Licensee or the general public, the Open-Source Components, or any information that has been made publicly available by Licensor.

With respect to Confidential Information, Licensee shall: (a) hold it in strict confidence using at least the same degree of care Licensee uses to protect its own confidential information, but in no event less than reasonable care; (b) not disclose it to any third party without Licensor's prior written consent; and (c) use it solely as necessary to exercise Licensee's rights under this Agreement. The foregoing obligations do not apply to information that: (i) is or becomes publicly available through no fault of Licensee; (ii) was rightfully known to Licensee without restriction prior to disclosure; (iii) is independently developed by Licensee without reference to Confidential Information; or (iv) is required to be disclosed by law, regulation, or court order, provided Licensee provides Licensor with prompt prior written notice and reasonably cooperates with Licensor's efforts to seek a protective order.

10. General Provisions

10.1 Governing Law

This Agreement shall be governed by and construed in accordance with the laws of the State of Delaware, United States, without regard to its conflict of law principles. Any dispute arising under or relating to this Agreement shall be subject to the exclusive jurisdiction of the state and federal courts located in Delaware.

10.2 Entire Agreement

This Agreement, together with any Commercial Support Agreement executed by the parties, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, negotiations, and understandings, whether written or oral. In the event of a conflict between this Agreement and a Commercial Support Agreement, the Commercial Support Agreement controls with respect to support and service-level terms only.

10.3 Amendments

Licensor may update this Agreement from time to time. Updated versions will be made available at https://tabsdata.com/license, with at least thirty (30) days' advance notice of material changes.

(a) Free Use Licensees. For Licensees who do not hold a current Commercial Support Agreement, continued use of the Software after the effective date of a revised Agreement constitutes acceptance of the revised terms.

(b) Commercial Support Agreement Customers. For Licensees holding a current Commercial Support Agreement, amendments to this Agreement require a written instrument signed by authorized representatives of both parties. No amendment to the terms of this Agreement shall be effective against such Licensees solely by virtue of posting at https://tabsdata.com/license or continued use of the Software.

10.4 Assignment

Licensee may not assign this Agreement or any rights or obligations hereunder, in whole or in part, without Licensor's prior written consent, except in connection with a merger, acquisition, or sale of all or substantially all of Licensee's assets to a party that agrees to be bound by this Agreement. Any attempted assignment in violation of this section is void. Licensor may freely assign this Agreement.

10.5 Severability

If any provision of this Agreement is found to be unenforceable or invalid under applicable law, such provision shall be modified to the minimum extent necessary to make it enforceable, and the remaining provisions shall continue in full force and effect.

10.6 Waiver

Licensor's failure to enforce any right or provision of this Agreement shall not constitute a waiver of such right or provision unless acknowledged in writing by Licensor.

10.7 Notices

Notices under this Agreement shall be in writing and deemed delivered when sent by email to the address on record for each party, or when delivered by courier to Licensor at its principal place of business.

10.8 Export Compliance

Licensee shall comply with all applicable export control laws and regulations in connection with its use of the Software.

10.9 U.S. Government Users

The Software is "commercial computer software" as defined in FAR 2.101. U.S. Government users acquire the Software subject to the rights and restrictions of this Agreement.

Annex A — Illustrative Use-Case Reference

The following table illustrates how the license terms apply to common use cases, with concrete examples for each scenario. It is provided for informational convenience and is not a substitute for the Agreement text. In the event of any conflict, the Agreement controls.

Permitted uses — internal deployment

Use CaseExamplePermitted?

Internal data integration and dataflow development by Licensee's own personnel

A data engineering team installs Tabsdata on company servers and builds dataflows that move data from Salesforce and PostgreSQL into a Snowflake warehouse.

✓ Permitted

Developer evaluation and testing

A software engineer downloads Tabsdata locally, connects it to a test database, and writes publisher and subscriber functions to evaluate it before recommending it to their team.

✓ Permitted

Contractor building on behalf of Licensee

A freelance data engineer is hired by a company to design and configure Tabsdata dataflows on the company's infrastructure, exclusively for that company's benefit.

✓ Permitted

Permitted uses — internal platforms

Use CaseExamplePermitted?

Internal data-as-a-service platform serving multiple teams

A bank's central data platform team deploys Tabsdata as the engine of an internal data platform, serving 30 business units across the bank under a single deployment.

✓ Permitted

Shared internal service with internal cost allocation

A large enterprise runs a centralised data integration service powered by Tabsdata and charges individual business units a monthly cost-recovery fee based on their compute usage.

✓ Permitted

Multi-subsidiary deployment

A holding company installs Tabsdata centrally and uses it to move and synchronise data across five wholly-owned subsidiaries.

✓ Permitted

Professional services engagement

A consultancy installs and configures Tabsdata on a client's own infrastructure as part of a data engineering project. The client is the Licensee; the consultancy is acting on their behalf.

✓ Permitted

Permitted uses — open-source components

Use CaseExamplePermitted?

Forking and modifying the open-source repository

A developer forks the Tabsdata GitHub repository, modifies connector code to support a proprietary internal data source, and uses it internally.

✓ Permitted under Apache 2.0

Contributing to the open-source project

A company's engineers submit pull requests to the open-source repository, improving connector performance or fixing bugs.

✓ Permitted under Apache 2.0

Embedding open-source components in another tool

A company builds an internal tooling layer that imports Tabsdata's open-source Python SDK and connector libraries as a dependency.

✓ Permitted under Apache 2.0

Benchmarking and publishing results

A developer benchmarks Tabsdata against other data integration tools and publishes the results in a blog post or research paper.

✓ Permitted

Not permitted — resale and third-party services

Use CaseExamplePermitted?

Offering a managed Tabsdata service to external customers

A cloud services company wants to offer a fully managed data integration service — 'Data Pipelines as a Service' — to their own paying customers, powered by Tabsdata under the hood.

✗ Not Permitted

Reselling the software as a product

A software vendor wants to bundle Tabsdata as part of a data platform product they sell to enterprise customers. Note: this restriction applies to the integrated distribution (including proprietary components). The open-source components remain freely redistributable under Apache 2.0 independently of this restriction.

✗ Not Permitted

Building an external SaaS product on Tabsdata

A startup wants to build a SaaS data integration product where Tabsdata's engine handles all the data movement and versioning, and customers log in to a proprietary UI on top.

✗ Not Permitted

Providing data integration services to third-party clients using Tabsdata as the billable engine

An agency offers ongoing 'data integration as a service' to multiple client companies, running a shared Tabsdata instance where each client's data is processed and billed separately.

✗ Not Permitted

Not permitted — proprietary component restrictions

Use CaseExamplePermitted?

Embedding proprietary components without disclosure

A software company wants to ship a product that includes Tabsdata's enterprise binary (including proprietary components) to their customers, without informing Tabsdata, Inc.

✗ Not Permitted

Reverse engineering proprietary components

A developer attempts to decompile the Tabsdata enterprise binary to inspect and reproduce the proprietary transaction granularity logic for use in a separate project.

✗ Not Permitted

Permitted with risk caveat — AI agent (Tabby)

Use CaseExamplePermitted?

Use of AI Agent (Tabby) for dataflow generation

A developer uses Tabby to generate a subscriber function. The generated code contains a logic error that overwrites a production database table. Note: AI-generated dataflows, scripts, and configurations are suggestions only and must be reviewed and tested by Licensee before execution. Licensor is not liable for errors, data loss, or downtime resulting from execution of AI-generated content (see Section 5.2).

✓ Permitted, but at Licensee's Sole Risk

© Tabsdata, Inc. All rights reserved.