Integrations
Plyed connects to a few outside services. None of them are required — every integration is opt-in, and all of them are available on every plan.
| Integration | What it’s for | Where to connect |
|---|---|---|
| Figma | The AI builds sections straight from your designs | Account → Integrations — or just have the Figma app open |
| GitHub | Back up your project’s code to your own account | Git in the top bar |
| Sanity CMS | Structured content with an embedded Studio | The CMS panel in the left rail |
Account-wide vs. per-project
Section titled “Account-wide vs. per-project”Figma and GitHub connect once, in your account — every project can use them. Sanity is connected per project, since each site usually has its own content: the CMS panel stores the Sanity project ID and dataset in that project’s environment variables. MCP servers are per project too, and their configs are project files, so they travel with the code.
What about hosting?
Section titled “What about hosting?”Publishing isn’t an integration — it’s built in. Hit Publish and your
site goes live at <name>.plyed.cloud. You can also deploy the same project
to your own Vercel account; see
Publishing your site.
Your projects are plain Astro code in a folder on your Mac, so anything else you’d like to connect — analytics, forms, custom APIs — works the way it would in any Astro site. Keep keys in environment variables, and ask the AI to wire the service up for you.