Account Billing Boundary

Dineway account billing lives in Web and CLI flows, not in your generated site's Admin.

Your Admin is yours

The Dineway Admin inside a generated site belongs to that site. It is part of the output your agent creates for you, alongside the code, content, media, menus, and configuration.

Dineway does not embed membership, subscription, checkout, billing, or upgrade screens in that Admin. If you self-host the site or deploy it to your own server, your site remains yours.

What the Dineway account controls

Your Dineway account is used by the public Web product, CLI, and Skills. Internally it is backed by Forgeway, but it is presented as a Dineway account.

Current plans:

  • Free Builder: $0, 1 Forgeway-hosted deployed site, no credits.
  • Starter: $39/mo, 1 Forgeway-hosted deployed site, 2925 credits.
  • Growth: $69/mo, 3 Forgeway-hosted deployed sites, 6900 credits.
  • Scale / Agency: custom pricing, 5+ Forgeway-hosted sites.

Self-hosted sites are unlimited on every plan.

Account limits and paid services can apply to:

  • place_search quota.
  • Deployments to Forgeway subdomains.
  • Hosted paid APIs such as Firecrawl, DataForSEO, and Forgeway-hosted AI interfaces.
  • Future cloud Managed Agent runtime hosting.

They do not apply to:

  • Your generated Dineway site.
  • Your site’s local Dineway Admin.
  • Deployment to your own server.
  • Using your own agent, local workflow, and provider credentials.

When onboarding appears

Onboarding can start from the Free Builder Onboard button on the public pricing page. It also appears when CLI or a Skill reaches an account limit or asks for a paid Forgeway-hosted capability. The CLI creates a Web handoff when logged in, prints a Dineway Web pricing or onboarding link, and then either exits for non-interactive commands or waits at an explicit user prompt for interactive flows. Registration, passwordless login, onboarding, checkout, billing, and usage-credit purchase happen in Dineway Web.

The Web onboarding flow is a five-step Dineway flow: set up your agent workspace, describe the restaurant, choose launch intent, copy the agent launch brief, then continue free or upgrade when a restaurant is ready to go live. The onboarding page includes a right-side Loom walkthrough and uses restaurant-specific prompts.

Logged-in public navigation should show a small avatar-only account control. Email, plan, account links, and Log out appear inside its dropdown. Account CTAs use Continue free.

Example:

Dineway account quota reached: place_search.
Open https://dineway.ai/pricing?source=cli&reason=place_search_quota to continue.

Dineway Web v1 does not provide a user-facing account API-key page. CLI and Skills use login-backed Forgeway credentials.

Before you publish

Billing is separate from review. Before publishing any generated site, ask your agent to audit it:

Audit this restaurant site before publishing. Check content accuracy, navigation, menu structure,
local SEO, media alt text, mobile layout, and any unresolved questions. Give me a short readiness
report, not just "looks good."

The agent should come back with specifics: what is solid, what needs your input, and what should be fixed before customers rely on the site.

Read the high-level pricing page for account limits and paid cloud services.