Skip to Content

Private Agents


When you run an integration, connectivity to your data is enabled through the agent(s) you have configured. There are two types of Jitterbit Agent Groups: Cloud and Private.

  • Cloud: The Jitterbit Cloud Agent Group consists of a set of Jitterbit Agents that are maintained and managed by Jitterbit. This option allows you to run all of your integrations in the cloud with a scalable, multi-tenant, fault-tolerant clustered Agent Group. The most common use case is a cloud-to-cloud integration. For details, see Cloud Agent Groups.

  • Private: You can also provision and manage your own Agents as Private Agent(s) and Private Agent Groups, such as on your own servers, within a corporate firewall, or on virtual private clouds. This option allows you to choose where your integration runtime environment operates and control which network your data travels and resides in. Private Agents allow you to use local files as sources or targets, add custom connectors, or use ODBC drivers. These are options unavailable with Cloud Agents.

You choose which Agent Group you want to use from within the Management Console, as described in Agents > Agent Groups.


Private Agents were formerly known as Local Agents.

Time Zone

The time zone used for schedules is that of the agent running the operation, unless the Override Schedule Agent Time Zone setting is enabled in your organization's policies. Private Agent time zones are determined by the time zone of the operating system of the Private Agent. It is highly recommended for all agents in a Private Agent Group to be running on the same time zone, or the times at which a configured schedule initiates the operation may be unpredictable depending on the specific agent being used.

When using agent version 10.85 / 11.23 or later, and the agent is using a time zone that observes daylight savings, these actions occur during a daylight saving time switch:

  • When a once-daily schedule is set between 2 - 3 AM, the scheduled operation will run at 3 AM on the second Sunday of March.

  • When a once-daily schedule is set between 1 - 2 AM, the scheduled operation will run on the second instance of 1 AM on the first Sunday of November.

A known issue exists for the above scenarios when using agent version 10.84 / 11.22 and earlier.


For schedule consistency, it is recommended to use a time zone that does not observe daylight saving time, such as UTC (Cloud Agents use UTC by default). If using a Private Agent, you can use the Override Schedule Agent Time Zone setting and select Etc/UTC.