Welcome to Mochi Deploy
Mochi Deploy brings reviewable change management to your Aprimo configuration, so you always know what changed, who approved it, and where it went.
Aprimo lets you configure a lot: fields, content types, classifications, rules, and more. Mochi Deploy adds change management on top of the setup you already have. You get a clear record of what changed and who changed it, an optional review step for changes that need a second look, and a clear path to carry a change from a sandbox up to production, whether you start it yourself or let it run automatically.
It comes down to three simple ideas:
- Environments are your Aprimo instances: a sandbox, a QA instance, your production instance. You connect each one once.
- Change sets bundle the configuration items you've changed so you can move them together.
- Pipelines carry a change from one environment to the next. Add a checkpoint along the way when a change should be approved before it lands.
Find your way around
Set up your environments and create your first change set.
The handful of ideas behind Mochi Deploy: environments, change sets, pipelines, and approvals.
Step-by-step answers to specific tasks, from setting up approvals to repairing broken references.
A glossary, what Mochi tracks in Aprimo, roles and access, and pricing.
What Mochi Deploy is not
Mochi Deploy is for your Aprimo configuration: fields, content types, classifications, rules, and the like. The review, approvals, and delivery you'll read about here all apply to configuration changes only. Reviewing, approving, and delivering your content, your assets, or your workflows isn't what Mochi does.