Get components built outside your organization
Agencies, freelancers, partners and vendors can build UI for you. Usually that means giving them access to your repository, your design system or a staging environment. With the Myop marketplace, an outside contributor works on one component and sees nothing else of yours.
How it works
- Post a request. Turn a component into a request and share its private link. The request carries a description, a contact address, a deadline and a status. The link is unlisted, so only people you send it to can open it.
- They build it in their own space. A contributor opens the link and takes a copy of that component into their own Myop organization. They build and test it there, with their own tools.
- They submit. When it's ready, they submit their implementation back to your request.
- You review and take the one you want. You see the submissions for your component. Claiming one copies that version into your organization, where it goes through your normal environments and rollout like anything else you own.
What the contributor can and cannot see
| They get | They never get |
|---|---|
| The component in your request: its current version and description | Access to your organization |
| A copy in their own organization to work on | Your other components, flows or experiences |
| Your environments, releases, analytics or API keys | |
| Your users, your data, or your codebase |
The connection runs one way. They work on a copy, and nothing they do touches your organization until you claim it.
Run outside code safely
What you claim is still code written by someone outside your company. Pair the marketplace with component isolation so contributed components render in a sandboxed iframe with no access to your page, your cookies or your storage, until you decide to trust them.
Get started
To set up the marketplace for your teams and partners, book a technical intro.