- Execution and scheduling: The agent enables the execution of pipelines within . It acts as the engine that carries out the tasks defined in the pipelines.
- Data locality: Your data will remain in the region your agent is running in, allowing you to conform to data locality limitations set by your organization or law.
- Scalability: The agent can scale up by running multiple instances concurrently, allowing for increased workload handling based on the user’s requirements.
You need a to run Streaming pipelines. This agent type has its own architecture considerations and installation procedure, which are covered under Create a .
Video example
Expand this box to watch our video about agent.Architecture
The is required for to schedule and execute the pipelines you create. While agents can be installed manually on your cloud platform, a Matillion Full SaaS deployment is provided for you when you create your first project and this agent (hosted by Matillion) can be seen from the Manage Agents page in . Thus, you don’t need to install your own agent if you don’t want to.
What is a data plane?
A data plane refers to an abstract concept that represents an execution environment. This execution environment, such as AWS Fargate, is used in conjunction with an agent provided by Matillion as a Docker image. The data plane serves as the infrastructure or environment where the agent instances operate. The agent instances, when deployed within the data plane, collectively form the agent. Each agent instance is responsible for executing individual pipeline tasks. These pipeline tasks typically involve interactions with various data sources, including a data warehouse. The data plane provides the necessary resources and infrastructure for the agent instances to execute the assigned pipeline tasks and perform data-related operations.What is agent?
The agent is a software component responsible for executing the pipeline tasks within the specified environment. It serves as the execution engine for the pipelines and interacts with the agent gateway to receive the pipeline tasks that need to be executed. The agent communicates with the agent gateway using an egress-only method, meaning it can send requests and receive responses but can’t accept incoming connections. The pipeline tasks that are sent to the agent originate from platform. These tasks define the specific operations and transformations to be performed on the data within the pipeline.What is agent manager?
The agent manager is an application or tool that facilitates the creation, configuration, and management of agents within ecosystem. It is typically accessed through , where you can manage various aspects of the data pipelines. With the agent manager, users can create and define configurations for installing and deploying agents. This includes specifying settings such as the agent image, environment variables, resource allocation, and any other required parameters. The agent manager provides a user-friendly interface or set of commands to simplify the process of configuring and setting up agents.The agent manager offers functionality for managing agents in compatible environments like AWS ECS Fargate. This includes features such as automatic updates, where the agent manager handles the process of updating agents to newer versions seamlessly. This ensures that agents deployed in compatible environments remain up to date with the latest features, bug fixes, and security patches. This means agent updates are controlled by Matillion, and as such, the user isn’t required to manually update the agent themselves.
Matillion Full SaaS vs Hybrid SaaS
provides two deployment models: Full SaaS and Hybrid SaaS.- With Full SaaS, Matillion manages the entire infrastructure, including agent deployment and security measures. Matillion ensures seamless updates and robust security protocols. The Matillion-hosted agent handles the execution of tasks, and customer secrets are securely stored in a Matillion-hosted secrets manager.
- With Hybrid SaaS, you deploy and manage your own agents within your own cloud infrastructure. This gives you full control over security measures, network isolation, access control, and where your secrets are stored. This option is available for Enterprise edition customers only.
- Custom JDBC drivers.
- SAP ODP.
- NetSuite SuiteAnalytics.
- Bash Script.
- Python Script. Use Python Pushdown instead in a Full SaaS deployment (Snowflake only).
Matillion Full SaaS
Every Matillion account is provided with an agent hosted by Matillion, providing a true zero-install experience. If your projects are set up to use Matillion’s Full SaaS infrastructure then there is no need to be concerned with managing the agent–this is handled by Matillion. There’s no setup needed for a Full SaaS solution—it’s available for you to use straight away. If you need to allow any access from the Matillion Full SaaS agent to your data plane, you’ll find the IP addresses here.Hybrid SaaS
If your account is on our Enterprise plan, you also have the option to install our agent software within your own cloud infrastructure and data plane. This is may be beneficial if:- Your data locality requirements need the agent to run in a specific region that Matillion doesn’t currently provide agents in.
- You aim to achieve faster processing speeds by locating the agent close to your applications, databases, and cloud data warehouse.
- You need to access systems (such as database or file storage) that only have network access from within your VPC/VNet.
- You have specific agent scaling requirements that a Matillion Full SaaS agent doesn’t support.
- You need to use any of the Hybrid SaaS pipeline components listed above.
Migrating from Full SaaS to Hybrid SaaS
Projects are either Full SaaS or Hybrid SaaS, and can’t switch between the two. If you want to move Full SaaS workloads to Hybrid SaaS infrastructure, you need to perform the following steps:- Install the Hybrid SaaS agent in your infrastructure.
- Create a new project that uses your Hybrid SaaS agent.
- Recreate any secrets in the new project.
- Export and Import the pipelines from the Full SaaS project to your new Hybrid SaaS project.
- Recreate any schedules in the new project.
Agent version tracks
In a Hybrid SaaS deployment, it’s important that you always use a currently supported version of the agent, which means you will be required to update your agent from time to time. As we recognize that it’s not always possible or convenient to update as soon as a new agent version is released, we offer a choice of release cadences, which we call version tracks. The choices are Current and Stable:- Current: Supports the latest features and has a faster cadence for releases. This is usually twice a week, typically on a Tuesday and Thursday, though this may vary. These releases may include new features, bug fixes, and security patches. This track is ideal if you want to access the latest features as soon as they are available, and are able to update your agent frequently.
- Stable: Has a slower, more predictable cadence for releases. This is once per month, on the 1st of the month. Features added to a Stable release have previously been available on a Current release. We take a cut of the Current track on the first day of each month, and after a period of testing and verification we release this as the Stable version on the first day of the subsequent month. This means that any new features in a Stable release have been available for at least one month on the Current track.
- Changing the ‘s version track does not update the itself. You must update the image URI for the service in your cloud provider. If you don’t, the version may show as “Out of support”.
- If you change the state from Current to Stable and update the installed service, pipelines created using a newer (Current) version might not run as expected on an older (Stable) version.

