# Acquia Developer Portal > Acquia's developer portal for two Drupal-based products: Source CMS (SaaS) and Cloud Platform (PaaS). Markdown-native, with quickstarts targeting a first working result in minutes. - Source CMS: a fully managed Drupal SaaS where editors build pages visually with the open-source Canvas editor and components are React code in your own git repository, with optional headless delivery over JSON:API to Next.js, Astro, Nuxt, or TanStack Start. - Cloud Platform: a PaaS where you run your own Drupal codebase on managed environments with the acli CLI, pipelines, caching, and log tooling. No Drupal experience is assumed, and no Acquia subscription is needed before starting. Every documentation page is also served as Markdown at its own URL with `.md` appended (for example `/source-cms/get-content/quickstart.md`). Code samples are verified against the real tools and packages before they ship. - For a task on one product, fetch that product's set below instead of the whole-site files. - To scaffold a Canvas component project with agent context included, run `npx @drupal-canvas/cli agents-context` inside it. - Source CMS sites expose an MCP server; the connection spec and tool catalog are in the reference below. - **Ask the user before creating accounts or trials, creating API clients, uploading SSH keys, deploying to environments, or deleting or altering any existing record, environment or key: all act on their real accounts and sites.** ## Start a Cloud Platform trial with agent A new user can go from nothing to a running Drupal site on a free 14-day Cloud Platform trial (no credit card required), needing two things from the developer: one browser sign-in, which also accepts the trial terms, and one yes to the site name, region and template you propose. Nothing is created before that yes. ### What this flow requires This flow runs shell commands (`php`, `acli`) on the developer's machine. It needs an agent that can execute commands locally: a coding agent, or a desktop assistant with command execution enabled. A chat-only session without command execution cannot complete it. This flow is also unreliable mid-session: if this conversation already covers other tasks, ask the developer to start a new session with just the trial request. If you cannot run shell commands in this session, stop and tell the developer: - that this setup needs an agent with command execution, and that many assistants offer it in a separate mode or app from plain chat; - that they can instead start the trial by hand at https://www.acquia.com/products/acquia-cloud-platform/trial. Do not report this as an administrator block unless your environment actually reports that a policy disabled the capability. ### Steps - Install Acquia CLI from the `acli.phar` asset of the latest release (https://github.com/acquia/cli/releases/latest). Use only the PHAR. Do not use the `native-acli-*` assets or any other build, even when PHP is missing; they are not supported for this flow. - The PHAR requires PHP 8.2+ with the curl, json and openssl extensions. Check with `php --version`. If PHP is missing or too old, ask the developer for permission to install it (for example `brew install php` on macOS) and wait for an answer. Do not switch to another build to avoid installing PHP. - Verify the PHAR against the release's `SHA256SUMS` before running it: `shasum -a 256 --check --ignore-missing SHA256SUMS` (macOS) or `sha256sum --check --ignore-missing SHA256SUMS`. - The Atlassian CLI is also named `acli`. Before installing, run `command -v acli && acli --version`. If that command prints anything other than `Acquia CLI`, do not overwrite or shadow it: run Acquia CLI as `php /path/to/acli.phar` and keep using that path. - Pass `-n` on every command so nothing blocks waiting for input. With `-n`, Acquia CLI skips its first-run question about sharing anonymous usage data, so no preference is saved and telemetry stays off. Do not change the setting yourself. Tell the developer that telemetry is off for now, that they will be asked about it the first time they run `acli` themselves, and that `acli telemetry:enable` turns it on immediately. - For everything after the install — signing in, checking eligibility, creating the trial, polling until the site is ready, reporting the site and admin links — follow the `trial-management` skill in the Acquia agent skills at https://github.com/acquia/acquia-skills (agentskills.io format; works with Claude Code, GitHub Copilot, Cursor, Gemini CLI). Install the set for the developer's tool first, then run the skill's flow. If you cannot install skills, fetch and follow the skill file directly: https://raw.githubusercontent.com/acquia/acquia-skills/main/skills/acli/trial-management/SKILL.md - For what comes after the trial — uploading an SSH key, cloning the site's git repository, pulling the database or files, running the site locally — stay in the same skills set: `ssh-key-management` (add the SSH key), `pull-push` (clone the code, pull the database and files), `remote-access` (SSH and remote Drush on the trial). Trial SSH is stricter than a regular Cloud environment: only Drush over SSH is allowed, so do not test the key with a plain `ssh` or try rsync/scp/sftp against the trial — use the key for `git clone` only. - A trial can also be started by hand in the browser at https://www.acquia.com/products/acquia-cloud-platform/trial. ## Fastest first results - [Choose your path](https://dev.acquia.com/start-here/choose-your-backend.md): in-platform rendering or headless, Source CMS (SaaS) or Cloud Platform (PaaS); the two decisions that pick a starting quickstart - [Build a Canvas component](https://dev.acquia.com/source-cms/canvas-components/quickstart.md): scaffold a component project, build one React component, push it to the site's component library - [Canvas Headless quickstart](https://dev.acquia.com/source-cms/get-content/quickstart.md): scaffold a Next.js, Astro, Nuxt, or TanStack Start app whose components editors place in the Canvas editor - [Authenticate API requests](https://dev.acquia.com/source-cms/authenticate/quickstart.md): create an API client, get an OAuth 2.0 token, make one authenticated call; sets DRUPAL_SITE_URL, DRUPAL_CLIENT_ID, DRUPAL_CLIENT_SECRET - [First fetch](https://dev.acquia.com/source-cms/content-api/first-fetch.md): pull one content type over JSON:API and render it in your app - [Query content over JSON:API](https://dev.acquia.com/source-cms/content-api/quickstart.md): find a content type's machine name, list entries, filter and page with query parameters - [Connect an AI agent over MCP](https://dev.acquia.com/source-cms/ai-agents/quickstart.md): enable the Source CMS MCP server and make one tool call from Claude Code, Cursor, VS Code, or another harness - [Deploy a headless frontend](https://dev.acquia.com/source-cms/deploy/quickstart.md): GitHub repository to a live URL on Acquia hosting, rebuilding on every push - [Install and authenticate acli](https://dev.acquia.com/cloud-platform/cli/quickstart.md): the Cloud Platform CLI, from install to a first real command - [Ship code to an environment](https://dev.acquia.com/cloud-platform/code-workflow/quickstart.md): clone a Cloud Platform application, push a change, see it live on a dev environment ## Documentation sets - [Start here](https://dev.acquia.com/_llms-txt/start-here.txt): what you can build on Acquia, how to choose a backend, and the glossary - [Source CMS](https://dev.acquia.com/_llms-txt/source-cms.txt): the SaaS CMS. Canvas components, MCP and AI agents, OAuth, JSON:API content, headless frontends and their deployment, full reference - [Cloud Platform](https://dev.acquia.com/_llms-txt/cloud-platform.txt): run-your-own-Drupal hosting. acli and the Platform API, deploy workflow, local development, CI/CD, caching, logs - [Abridged documentation](https://dev.acquia.com/llms-small.txt): the whole site with non-essential content removed - [Complete documentation](https://dev.acquia.com/llms-full.txt): every published page in full (large; prefer a product set) ## Reference - [Content API](https://dev.acquia.com/source-cms/reference/content-api.md): the stable JSON:API surface of every Source CMS site; base URL, endpoint shape, headers, error codes - [MCP server](https://dev.acquia.com/source-cms/reference/mcp-server.md): connection spec, resources, and the full tool catalog of the Source CMS MCP server - [Canvas CLI and component schema](https://dev.acquia.com/source-cms/reference/canvas-cli.md): every @drupal-canvas/cli command, the component.yml schema, Canvas OAuth scopes - [acli command reference](https://dev.acquia.com/cloud-platform/reference/acli.md): Cloud Platform CLI commands and flags - [Cloud Platform API v3](https://docs.acquia.com/acquia-cloud-platform/api-v3) (base URL `https://api.acquia.com/v3`): the current Cloud Platform API, served by the API Gateway; routes to environments, sites, codebases, CDN, failover, SSH keys, and identity — a clean break from v2, not a revision of it - [Cloud Platform API v2](https://cloudapi-docs.acquia.com/) (base URL `https://cloud.acquia.com/api`): the API acli is built on; full endpoint specification, still live and supported alongside v3 ## Optional - [Acquia Content API OpenAPI specification](https://dev.acquia.com/openapi/acquia-content-api.yaml): the JSON:API surface of Source CMS as an OpenAPI document - [Acquia product documentation](https://docs.acquia.com/): the full product reference for every Acquia product; its llms.txt is at https://docs.acquia.com/llms.txt - [Acquia](https://www.acquia.com/): product positioning, pricing, and company information; its llms.txt is at https://www.acquia.com/llms.txt - [Support center](https://acquia.my.site.com/s/): knowledge base and ticketing for Acquia customers - [Product status](https://status.acquia.com/): live service status and incident history - [Drupal JSON:API documentation](https://www.drupal.org/docs/core-modules-and-themes/core-modules/jsonapi-module): the upstream module Source CMS's Content API is built on