# banchi > banchi rents subdomains under banchi.app for connecting a customer's existing web service. It provides supported DNS configuration, not application hosting. Documentation checked 2026-09-10; live-test dates are stated separately in the manuals. Canonical management and API origin: https://banchi.app ## Manuals - [banchi-connect Skill](https://banchi.app/skills/banchi-connect/SKILL.md): Start here for AI-assisted setup. Identify the actual hosting product and deployment, fetch current official provider instructions during the task, check costs and user authorization, then configure and test. If current sources or the deployment cannot be confirmed, stop before dependent changes. This is a portable instruction file, not an MCP service or an API credential. - [AI setup handoff — 日本語](https://banchi.app/guide#ai) / [English](https://banchi.app/guide-en#ai): Copyable request and downloadable Skill; a person reviews the approach before setup. - [日本語・接続ガイド](https://banchi.app/guide): Human-oriented provider selection, setup, diagnostics and limits. - [English connection guide](https://banchi.app/guide-en): English version of the human guide. - [日本語・技術導入マニュアル](https://banchi.app/technical-guide.md): Detailed provider steps, Caddy and nginx/Certbot examples, verification commands, application URLs, API contract and evidence. - [English technical setup manual](https://banchi.app/technical-guide-en.md): Detailed machine-readable counterpart with the same constraints and evidence. ## Additional provider instructions The provider selection follows the ten leading hosting-experience choices in State of JavaScript 2025, cross-checked against Stack Overflow 2025. It is not worldwide market share among solo developers. AWS, Azure and Google Cloud are mapped to concrete services; Cloudflare Pages and Workers are two paths for one provider. These six additional services have official-documentation-based instructions, not completed banchi live tests. - [AWS Amplify Hosting — 日本語](https://banchi.app/guide#amplify) / [English](https://banchi.app/guide-en#amplify) / [technical details](https://banchi.app/technical-guide-en.md#amplify): Usage charges; inspect routing and certificate CNAME names. Stop at parent verification or NS requirements. - [Firebase Hosting — 日本語](https://banchi.app/guide#firebase) / [English](https://banchi.app/guide-en#firebase) / [technical details](https://banchi.app/technical-guide-en.md#firebase): Conditional hostname verification; parent banchi.app verification is not available. Hosting differs from App Hosting and paid dynamic integrations. - [Azure Static Web Apps — 日本語](https://banchi.app/guide#azure) / [English](https://banchi.app/guide-en#azure) / [technical details](https://banchi.app/technical-guide-en.md#azure): External-DNS CNAME path; TXT and paid-plan requirements vary by configuration. - [Heroku — 日本語](https://banchi.app/guide#heroku) / [English](https://banchi.app/guide-en#heroku) / [technical details](https://banchi.app/technical-guide-en.md#heroku): Paid compute, unique herokudns.com target and ACM; Eco now supports automatic certificates. - [DigitalOcean App Platform — 日本語](https://banchi.app/guide#digitalocean) / [English](https://banchi.app/guide-en#digitalocean) / [technical details](https://banchi.app/technical-guide-en.md#digitalocean): DNSSEC-enabled domains are unsupported. Check before purchase; use externally managed DNS. - [Google Cloud Run — 日本語](https://banchi.app/guide#google-cloud) / [English](https://banchi.app/guide-en#google-cloud) / [technical details](https://banchi.app/technical-guide-en.md#google-cloud): Direct mapping requires parent ownership. Firebase Hosting routing requires Blaze, a 60-second timeout limit and cookie compatibility; normally only __session is forwarded. An external load balancer has separate costs. Survey sources: [State of JavaScript 2025](https://2025.stateofjs.com/en-US/other-tools/) and [Stack Overflow 2025](https://survey.stackoverflow.co/2025/technology). ## Service and API constraints - Normal DNS connections are DNS-only; traffic goes directly to the customer's hosting. The customer manages the app, certificates, renewal and hosting costs. - JPY 500 including tax per rented address per year, automatically renewed; customers in Japan only. Multiple addresses per email have separate contracts. Operator-only free exceptions are not a public plan. - Supported records: A, AAAA, CNAME, web TXT, CAA; standard five records including system fallback and verification records. A missing user root target uses one system fallback slot. - Names are @ or full names within the rented namespace, including multiple child levels. No email DNS, NS delegation, wildcard DNS or other customers' names. A CNAME cannot share its name with other records. - GitHub Pages, Cloudflare Pages across accounts, Vercel, Netlify and an IPv4/Caddy VM have scoped live evidence. Direct cross-account Workers/R2 Custom Domains are not offered. Application migrations and certificate renewals are not automatically verified. - [Cloudflare Workers entry setup](https://banchi.app/technical-guide-en.md#workers-r2): create a small Pages entry in the customer's Worker account, bind APP to the existing Worker, register the rented hostname in Pages, and set banchi's CNAME to the production pages.dev target. Keep code, data, secrets, Cron and Queues in the original Worker. This is customer-side setup, not banchi application hosting or an arbitrary-URL relay API. - The entry allows only the exact configured HTTPS origin; pages.dev and Preview return 404. Preview has no production Service binding. Preserve application authentication: Access/WAF on the original public URL is not inherited. Check actual assets, OAuth, cookies, forms and streaming against the manual's scoped evidence. Free/existing-plan allowances may cover the entry; additional charges are not inevitable. - Existing management API uses the owner's HttpOnly session cookie and ownership checks; writes require same-origin validation. No customer API key, PAT, OAuth client credential or certificate-renewal token is provided. Do not export cookies, login links or secrets. - Public reads: GET /api/config and GET /api/search?q=...&parent=banchi.app. Availability is not a reservation. Signed-in config responses may include personal data. - DNS PUT replaces the complete desired record set and requires the current plan_version in individual-record format. Omitted records are removed; preserve retained IDs and exclude system/deleting rows. On conflicts or uncertain results, reread before changing anything. See the technical manual before using mutations. - Diagnosis checks root DNS and HTTPS only; it may update connection state. LIVE does not prove login, forms or payments. Manual DNS-01 does not provide automatic renewal. ## Account and support - [Your addresses](https://banchi.app/app): Sign-in and management UI, including target-specific renewal cancellation. - [Report a problem](https://banchi.app/help): Private report form; no GitHub account required. Do not submit secrets or authentication links. - [Terms](https://banchi.app/terms): Contract and lifecycle conditions; English summary is available on the page. - [Privacy](https://banchi.app/privacy): Information handling. - [Legal disclosure](https://banchi.app/legal): Seller and statutory information.