Search docs.molo17.com

    Licensing

    Gluesync is licensed with a signed JWT in a .dat file. Core Hub verifies it locally. There is no license server and no phone-home, which is why the same file works in an air-gapped rack.

    What is in a license

    Each .dat carries:

    • Type (Trial, Enterprise, Enterprise with Advanced Security, or NFR)

    • Enabled features

    • Product identification

    • Expiration date

    The token is signed with a public/private key pair. Tampering invalidates it. You can inspect the payload (not the signature’s meaning) at jwt.io.

    Types

    Type Duration What it includes

    Trial

    30 days

    Full product capabilities except Advanced Security. This is what a trial kit ships.

    Enterprise

    As agreed (commonly 1 or 3 years, or a fraction)

    Production use of the platform except end-to-end node-to-node encryption.

    Enterprise with Advanced Security

    As agreed

    Everything in Enterprise, plus AES-256 node-to-node data encryption. See Security.

    NFR (not for resale)

    As agreed

    Partner, demo, or internal MOLO17 use. Same Control Plane surfaces; not a production entitlement.

    Check or replace it

    Three places tell you what you are running:

    1. Control Plane — Settings (gear icon, upper-right corner) → License. Type, expiration, and upload of a new .dat. UI-focused steps: License management.

      Uploading a .dat from the Control Plane is supported on Docker Compose deployments.

    2. Core Hub log — look for a line like:

      JwtLicenceKeyComponentSetup INFO - Licence key info [expireDate: Sun Oct 29 09:35:40 UTC 2023, plan: trial]
    3. jwt.io — paste the file contents to read type and expireDate yourself.

    When a license expires you can still open the Control Plane, but every pipeline is paused until a valid file is applied. MOLO17 watches commercial expirations and typically contacts you before renewal; do not rely on that as the only reminder — the UI also banners upcoming and actual expiry.

    Get a license

    sales@molo17.com — usually within one business day.

    Say what you need: use case, connectors, Advanced Security or not, deployment shape (on-prem, cloud, air-gapped), and timeline. For a first look, the trial kit is faster than a custom file: Get Gluesync.

    FAQ

    Can I extend my trial?

    Yes, but not from the product. A license is a signed file with its own expiration date, so only MOLO17 can issue a new one. Write to sales@molo17.com, or to the person who sent you the trial, and say what you still need to evaluate. You receive a new .dat file that you apply as described in How do I install a new license file?. You do not reinstall anything and your pipelines are kept.

    How do I convert a trial to a paid license?

    The same way. When the commercial agreement is in place, MOLO17 sends an Enterprise or Enterprise with Advanced Security .dat file. Replace the trial file with it. The license is a separate file: the pipelines, entities and connections you built during the trial stay as they are.

    How do I install a new license file?

    Use the way that matches your deployment:

    • Docker Compose, including the trial kit. In the Control Plane, select the Settings gear icon in the upper-right corner, then License, choose the .dat file, and select Upload file. The page then shows the new type and expiration date. See License management.

    • Any other deployment. Put the file in the configuration folder of Core Hub under the name gs-license.dat, replacing the old one. In the kits this is shared/gs-license.dat, mounted as /opt/gluesync/shared. Core Hub reads the file again every hour, so restart Core Hub to apply it immediately.

    Uploading a license checks and saves it, but it does not start any entity. After an expiration, open each pipeline and start the entities that were stopped.

    What happens when the trial expires?

    • Before the date. During the last 15 days the Control Plane header shows the banner Your license is expiring soon in the next N days, please contact our support, and Core Hub logs a warning at every start.

    • After the date. A trial license has no grace period. Core Hub checks the license when it starts and every hour. At the first check after the expiration date it stops all the entities of every pipeline, and it refuses to start them again: the answer is The license expired. Please contact sales@molo17.com. The header banner turns to Your licence is expired on <date>, please contact our support.

    • What stays available. You can still sign in to the Control Plane, open the pipelines and the License tab, and upload a new license. Pipelines, entities, connections, users and checkpoints are not deleted.

    Because the entities are stopped, replication does not run until you apply a valid license and start them again. They resume from their last checkpoint. Make sure the source keeps its change log long enough, for example the WAL kept by the replication slot of a PostgreSQL source, so that no change is lost while replication is stopped.

    Do paid licenses stop at the expiration date too?

    Not immediately. When a license that is not a trial expires, Core Hub keeps replicating for 30 more days, and the header banner and the Core Hub log warn that the instance will stop working. After the 30 days it behaves like an expired trial. Do not rely on this period: ask for the renewal before the date.

    How do I check when my license expires without opening the Control Plane?

    Read the Core Hub log: at start it prints a line such as License key info [expireDate: <date>, plan: trial]. You can also call GET /global-config/license of the Core Hub REST API, or the get_license_info tool of the Core Hub MCP server: both return status (ACTIVE, EXPIRING, EXPIRED_GRACE_PERIOD, EXPIRED, INVALID or UNREADABLE), valid, plan and expiresAt.

    I received a log message saying that the license expired, but my Control Plane shows a valid one

    The message is written by the installation that read that file. Look for another, older installation or kit that still runs with the trial file, for example a test environment that you thought was switched off. Each installation reads only its own gs-license.dat.

    Does Gluesync need internet access to check the license?

    No. Core Hub verifies the signature of the file locally, with no license server, so the same file works in an air-gapped environment.