For your team

Run the tools behind the campaign.

Bring content, analytics and automation services into the same operating workspace.

Flight paths artwork / 06

Product workflow illustration

A useful next step

The landing page is only one part of a campaign. A CMS, a workflow and a data store also need owners, configuration and a reliable place to run. Choose the services that fit your team and keep the handoff to technical colleagues clear.

What to consider

Put it into practice

Give the workflow an operating owner

Configure the selected automation service and its connections. Test a real input, inspect the result and agree who will handle failures and credential changes.

Choose the supporting software

The catalog includes data, automation, AI, monitoring and other packaged software. Read each service guide before deployment and review its configuration and dependencies.

Decide who operates each part

Document the infrastructure boundary, access model and responsibilities for configuration, upgrades, data and recovery. Agree on a handover before production use.

Choose the supporting software ↗Deploy the code you own ↗

Detailed instructions are maintained in the product documentation.

Questions before you start

Can I connect my existing tools?

Check the selected service’s supported integrations and credential requirements. Moltern runs the service; integration behavior belongs to that software.

Does every service have the same setup?

No. Required variables, dependencies, storage and access differ. The individual service guide explains the setup.

Is infrastructure ownership the same as a security certification?

No. Infrastructure placement and operational responsibility are design choices, not claims of independent certification.