# Mockoon Cloud vs Free Hub Mocks

**Short answer:** A mock cloud is a paid collaboration layer for a separately maintained mock; a Hub hosts the mock and the docs together from the spec, so the hosted surface cannot be out of sync. The first is a shared mock; the second is a shared contract.

## What a mock cloud provides

Hosted access and collaboration around the mock file. It is the right tool when the mock is a standalone artifact a team shares.

## What the Hub provides

| Property | Mock cloud | Hub |
| --- | --- | --- |
| Hosted surface | Mock | Mock + docs |
| Source | Mock file | Spec |
| Sync | Manual | On publish |
| Agent tools | Separate | From spec |

## Why the shared host matters

When the mock and the docs are hosted from the same spec, they are aligned by construction and a reader and an agent see the same surface.

## The decision rule

Use the mock cloud for a standalone shared mock. Use the Hub when the mock and the reference should be hosted together and stay synced.

This is part of the [Powerduck vs Mockoon comparison](https://www.powerduck.com/blog/powerduck-vs-mockoon/). Next, read [stateful scenarios](https://www.powerduck.com/blog/stateful-scenarios-mockoon-vs-powerduck/).

