For anyone who wants to launch and validate an idea, hassle-free

AI built the app.
BellD ships it.

Import a repo and see what is missing before launch. Once it is fixed, BellD keeps watching.

No credit card needed

Find the problem,
and the next step.

More than a score. Every finding comes with its location and impact, AI prepares a fix, and the fix is evaluated again.

Sample content, not a real scan result

Order AssistantRevision 7

1 / 3 · Finding

HighHard-coded credential in sourceBackend API Locationapps/api/src/config/payment.ts · line 18ImpactOnce public or deployed, others may gain payment access
Production is not affectedSee the fix
Order AssistantRevision 7

2 / 3 · Fix

// apps/api/src/config/payment.ts
- export const PAYMENT_KEY = "sk_test_••••";
+ export const PAYMENT_KEY = process.env.PAYMENT_KEY;
Needs a new variable PAYMENT_KEY; it takes effect once filled in
If this key ever leaked, regenerate it with the provider.
AI fix · waiting for your approvalApprove and re-evaluate
Order AssistantRevision 7

3 / 3 · Re-evaluation

Build52 s
Scan0 findings
Startup checkPassed
Revision 8 is ready to go liveBefore it goes live, have the team check the core features once more.

Live in three steps

Web AppAI AgentAI App

No need to learn deployment first. BellD reads your project and lines up what needs doing.

  1. 01ImportPaste a GitHub URL. The front end, back end and database are found automatically, and environment variables are listed up front.
  2. 02Understand the findingsRisk, location and reasoning together, not just a score. AI prepares a fix, and you decide whether to apply it.
  3. 03Fix, then go liveAfter approval it is evaluated again; once it passes, release with one click. URLs, HTTPS and custom domains are handled.

After launch,
BellD keeps watching.

Knows the parts

Knows which services make up your product and how they connect, so you do not have to draw the architecture yourself.

Stays available

Every revision is evaluated first. A revision with problems does not go live, and the running one keeps serving.

Cost safety

Credits are reserved before each call, with no overdraft, and going over a cap needs your OK. No surprise bill at the end of the month.

The capabilities you need,
ready to plug in.

AI, email, data and files, with credentials kept by BellD. Outside systems can call the same capabilities through the Bridge API, with permissions and usage controlled together.

AI generationai.generate
Emailemail.send
Data storagedata.kv
Filesstorage.object
Outside systemsBridge APIContract · permissions · usageCapabilities

Pay for what you use

BellD charges in Bell Credit (BC), deducting only what you use. Top up NT$100, 300 or 500 in the Console at NT$1 = 100 BC, with a one-time payment and no automatic recurring charges.

An account receives 1,000 BC when it first connects to GitHub, valid for 60 days. Each BellD account and each GitHub account can receive it only once.

App members are billed starting December 1, 2026: the first 1,000 members per workspace each month are free, and each additional member costs 5 BC per month.

For all rates, see Billing.

Before you start

Who is BellD for?

Anyone who wants to launch an idea and validate it, hassle-free. An AI-built web app, agent or prototype all work, and the front end, back end and database can live in one repo.

How do I run the first evaluation?

Sign in to the Console, choose “New app”, give it a name, then choose “Import a service”. After you connect GitHub you can pick a repository from the list, and the branch defaults to the repository's default branch; you can also paste a repository URL, and the branch defaults to main. Press “Create service” to start the first evaluation.

Will AI change my code on its own?

No. An AI fix is evaluated again first, and a new revision is created only after you approve; the original revision stays as it is.

Can costs suddenly spike?

No. Credits are reserved before every call, and nothing runs without enough balance; going over the monthly cap needs approval from an owner or admin.

Are my credentials safe?

Credentials are write-only once saved and cannot be viewed again; your app only uses them at runtime. Builds and evaluation run in an isolated environment.

Got an idea you want to try live?

Paste a repo URL and see what is missing before launch.

Import a repo