verapli
Sign inJoin free
Menu

Guides · hosting · Everyday developer services

Deno Deploy organization and app

In the new Deno Deploy console create an organization (permanent name and slug) and an app linked to a GitHub repo. Deploy Classic (dash.deno.com) shut down on 2026-07-20.

Researched · not yet run liveLast researched 25 October 2026 · Deno · provider site

Researched, not yet run live. Built from the provider’s official pages (linked below). A person hasn’t walked this flow end to end yet, so check each step against the source.
Do this with verapliJSON for agents

Steps

Steps marked “human step” are ones only you can do: verapli never signs in, submits, pays or accepts terms for you.

  1. Sign in to the Deno Deploy console

    The person signs in at console.deno.com. verapli never creates the account.

    • Guided by hand
    • Human step: You sign in

    Where: https://console.deno.com/

  2. Create an organization

    Create a Deno Deploy organization. Choose the name and slug carefully; neither can be changed later.

    • verapli co-pilot
    • Human step: You press submit
    • After: Sign in to the Deno Deploy console

    Where: https://console.deno.com/

  3. Create the app

    On the organization apps page press + New App, pick the GitHub repository (grant the Deno Deploy GitHub app access if it is missing), and set environment variables in the app settings. Or use deno deploy create from the CLI.

    • verapli co-pilot
    • Human step: You press submit
    • After: Create an organization
    If something goes wrong (1)
    • The repository does not appear in the list.: Use Add another GitHub account or Configure GitHub App permissions to give the Deno Deploy GitHub app access. [2]

    Where: https://console.deno.com/

Terms and gotchas

Plain-English summary, not legal advice. Each card links its source.

Can cost moneyThe rules say

Deno Deploy Classic was shut down on 2026-07-20; guides that mention dash.deno.com or deployctl describe the old platform. [1]

Worth knowingThe rules say

Organization name and slug are permanent; monorepos (app in a subdirectory) are not supported yet. [2]

Pricing

  • Free tier: 1M requests/month, 20 GiB egress, 10 hours active CPU, 10 active deployments.
  • Costs: Pro $20/month.

Source [3]

For agents

The same entry as JSON: /api/v1/entries/deno/deploy · requirements /api/v1/requirements/deno/deploy · terms /api/v1/terms/deno/deploy.

Remote MCP (read-only, no auth)
claude mcp add --transport http verapli https://verapli.com/mcp

> "What do I need for Deno Deploy organization and app, and how long will it take?"
  → tools/call requirements { "provider_id": "deno/deploy" }

Sources

  1. Deno Deploy Deno Deploy is a rework of Deploy Classic with a new dashboard; 2 regions; Deploy Classic (dash.deno.com) and subhosting v1 API shut down on July 20, 2026; start at console.deno.com, create organization, create app, deploy from GitHub or the dashboard. · accessed 25 October 2026 · official
  2. Getting started with Deno Deploy Organization names and slugs cannot be changed after creation; slug cannot match an existing Deploy Classic project; + New App on organization apps page; choose GitHub repo (monorepos not supported yet); Deno Deploy GitHub app permissions; deno deploy create CLI; app environment variables set in app settings. · accessed 25 October 2026 · official
  3. Deno Deploy pricing Free $0/month, 1M requests/month, 20 GiB egress, 10 hours active CPU, 10 active deployments; Pro $20/month. · accessed 25 October 2026 · official

Provider rules change. This page is generated from verapli registry version 2026.1025.316; spotted something out of date? Tell us. Deno is not affiliated with verapli.