---
title: "Code Export (Enterprise)"
description: "The terms on which selected enterprise customers receive the code for their own pipelines and run it on their own infrastructure."
url: "https://www.jsonify.com/legal/code-export"
---

# Code Export (Enterprise)

Last updated: November 17, 2026

Code Export lets selected enterprise customers receive the code for their own pipelines, kept up to date by git sync, and run it on their own infrastructure. It is available only where an Order Form says so.

In these terms, "Order Form" means the signed order form or statement of work between you and Trailing Comma, Inc., doing business as Jsonify ("Jsonify"), that names Code Export. "Terms" means the [Terms of Use](https://www.jsonify.com/legal/terms), or your signed agreement with Jsonify where you have one. Capitalized terms not defined here have the meaning given in the Terms.

## 1\. Availability

*   Code Export is offered to selected enterprise customers only, by agreement. Jsonify decides whether to offer it and for which pipelines.
*   It is enabled per pipeline. The pipelines it covers are listed in the Order Form or an annex to it.
*   It is not available on self-serve, free or trial plans.

## 2\. What Is Exported

"Customer Pipeline Code" means the pipeline-specific code Jason produces for you, for the pipelines the Order Form covers: extraction steps for your named sources, field mappings, the schema, validation rules and run configuration.

Jsonify delivers Customer Pipeline Code to a git repository you control, and updates it by commits while your Code Export subscription is active ("git sync").

## 3\. What Is Never Exported

"Jsonify Materials" means everything else Jsonify uses to build and run pipelines, including:

*   Factory, Jason and the repair system, and the hosted runtime and scheduler;
*   shared source libraries and reusable extractors used across customers, unless the Order Form lists a specific library;
*   proxy, browser, anti-bot and fetching infrastructure, and provider integrations;
*   secrets, credentials, API keys and internal tooling.

Jsonify Materials are not exported and are not licensed under these terms. Customer Pipeline Code is delivered so that it runs without Jsonify Materials. You supply your own proxies, browsers and infrastructure.

## 4\. Excluded Pipelines

Code Export is not available for:

*   Provider-sourced Data, meaning data obtained through a third-party fetch provider such as Bright Data;
*   pipelines that run on a connected account (logged-in access);
*   sources Jsonify classifies as blocked;
*   anything else the Order Form excludes.

## 5\. Licence

Jsonify keeps ownership of Customer Pipeline Code, consistent with [Section 10 of the Terms](https://www.jsonify.com/legal/terms#ownership).

Jsonify grants you a perpetual, worldwide, non-exclusive, non-transferable licence to use, copy, modify and run the Customer Pipeline Code for your own business purposes, including after your agreement ends.

You may not sublicense or redistribute Customer Pipeline Code, except as Section 6 allows.

## 6\. Open-Source Option

This Section applies only where the Order Form expressly says so, and only to the pipelines it names.

The Order Form picks one of two routes: (a) Jsonify publishes the Customer Pipeline Code under the Apache License 2.0; or (b) you may publish it under the Apache License 2.0 or the MIT License.

Once published, that code is available to anyone under that licence, and neither party can withdraw it. Jsonify keeps ownership of the copyright in it and of all Jsonify Materials.

Third-party components keep their own licences.

This Section grants no trademark rights. You may not use Jsonify's name or marks for the published code without Jsonify's written permission. A factual attribution line is permitted.

## 7\. Self-Hosted Operation and Responsibility

When you run exported code yourself, you are the operator of that collection. You are responsible for those runs complying with applicable law, source terms, robots.txt, rate limits, access controls and personal-data rules.

Jsonify's [Acceptable Use Policy](https://www.jsonify.com/legal/acceptable-use), source classification and collection policies govern runs on Jsonify's infrastructure. Jsonify does not apply them to, and does not monitor, runs on your infrastructure.

As a condition of the licence, you must not use exported code to defeat authentication, paywalls or payment requirements, or for any purpose the Acceptable Use Policy prohibits.

## 8\. Updates, Support and Warranty

Repairs and improvements reach you only as git sync commits, and only while Code Export is active. Jsonify may change or remove code in any commit.

Exported code is provided "as is". No warranty, and no uptime, delivery or repair commitment, applies to runs on your infrastructure. Any service levels in the Order Form cover Jsonify-hosted runs only.

## 9\. End of the Agreement

When your agreement or your Code Export subscription ends, git sync stops. You keep the code already delivered, under the licence in Section 5, or under the open-source licence in Section 6 if it was published.

Your access to Jsonify Materials ends as set out in the Terms.

## 10\. Order of Precedence

The Order Form overrides this page. This page overrides the Terms for Code Export only.

## 11\. Contact

For questions about Code Export, contact [paul@jsonify.com](mailto:paul@jsonify.com).

[Privacy](https://www.jsonify.com/legal/privacy)[Terms](https://www.jsonify.com/legal/terms)[Acceptable use](https://www.jsonify.com/legal/acceptable-use)[DPA](https://www.jsonify.com/legal/dpa)[Subprocessors](https://www.jsonify.com/legal/subprocessors)[Legal FAQ](https://www.jsonify.com/legal/faq)[Remove my data](https://www.jsonify.com/legal/remove-my-data)[Site owners](https://www.jsonify.com/legal/site-owners)[Code export (Enterprise)](https://www.jsonify.com/legal/code-export)
