Using Buildpane Creator

Development status: Creator account registration and Stripe test checkout are not currently open. The development site is being prepared for a Creator-only test. Production access and live payments are out of scope. Use synthetic project data in the test environment.

Start a project

When test access opens, choose New project, name it, and describe what you want in the Builder. A new project opens on Start building: a starter prompt written from the project's name is already in the message box for you to edit, replace (Another suggestion) or send with Generate my first draft. If you would rather not type, choose a Quick Start (Business website, Portfolio, Landing page or Online store), upload photos, answer a few click-to-choose questions, or start from a template — each writes the prompt into the box, and nothing is built or charged until you send it. Buildpane prepares a private managed development environment and opens its preview beside the conversation. The Builder can create a static site or, after an editor explicitly confirms it, prepare a managed development database for an app that needs saved data.

The preview is for development. It is not public application hosting and does not make a database-backed app public.

Work with the Builder

Use the chat to ask for changes and inspect the visible work as it happens. Creator includes project-file editing. Keep test projects synthetic; this development setup is not a production service or a long-term archive.

Internet access inside a Workspace

A Workspace reaches the internet over HTTP and HTTPS only (ports 80 and 443), through Buildpane's metered connection. Package installs, AI tools, web APIs and git over HTTPS work normally. Other connections do not:

• SSH git remotes ([email protected]:…, ssh://…) fail. Use the HTTPS address instead, for example https://github.com/you/project.git, with a personal access token when the repository is private.
• Email sending over SMTP (ports 25, 465, 587) fails. Send email through a provider's HTTPS API.
• Direct database connections to outside databases (for example PostgreSQL on 5432 or MySQL on 3306) fail. Use the database's HTTPS API, or the managed development database Buildpane prepares for the project.

Each funded interval includes a fixed allowance of outgoing internet transfer. When it is used up, further requests get a short Buildpane message (HTTP 402) until the next interval begins.

Build Credits and Compute Credits

Each new account receives one starter grant of 100 Build Credits for AI building and 200 Compute Credits for development infrastructure. The wallets are separate; 100 credits represents $1 of the applicable balance. Credits do not expire merely because you stop signing in. Open Credits to see both.

Compute balance and status

The Compute section shows what is available now, what is held for a running Workspace interval (unused holds return when the interval settles), any outstanding balance, and any converted Build Credits. A status line explains whether development can use Compute:

• Development is paused when available Compute Credits are at or below the 100-credit operation reserve, or when Compute Credits are used up while Build Credits remain. New development time is funded only from Compute Credits.
• Development is locked when Compute Credits and Build Credits are both used up, or an outstanding Compute balance is recorded. Development stays locked until you add Compute Credits.

While development is paused or locked, the Workspace shows a panel with the reason and Add Compute Credits. You can still sign in, open your projects, add Compute Credits when purchases are available, and contact support. Your files and your message draft are kept.

Adding Compute Credits

Choose an amount (500, 1,000, 2,500 or 5,000 Compute Credits, or a custom whole-dollar amount from $5 to $1,000). Declare personal or business use and enter your complete U.S. billing address, then review the credit amount, tax and total before paying with your saved card. Kentucky addresses are charged 6% sales tax in the test configuration; tax does not buy credits. A top-up first clears any outstanding Compute balance. After payment a receipt shows the credits added, the tax and the total, with a link to the invoice PDF.

If a payment result is uncertain, reopen the saved purchase and retry that same invoice rather than starting a new one. Until Compute purchases are opened on the development site, the amounts are shown but cannot be selected.

Compute activity

Compute activity lists every Compute movement, newest first, 25 at a time: starter grants, purchases, holds, usage, late usage, final adjustments and credits, Build Credit conversions, refunds and corrections. Usage is measured when a Workspace interval stops and is marked Estimate until final; it is normally finalized within 24 hours. If the final measurement is higher, the difference appears as a Final adjustment; if it is lower, the difference is credited to your Compute Credits as a Final credit. Amounts are shown exactly, including fractions of a credit.

The credit metering and account-retention work is not complete. The development test is for a limited Creator workflow and synthetic data, not validation of all infrastructure billing or long-term retention behavior.

Projects and publishing

The Creator direction allows three active projects. Archiving a project frees a slot without deleting it. Public application hosting and production publishing are not part of this test.

Test checkout

When the development checkout is enabled, it will use Stripe's test environment and test payment methods. Test checkout does not move real money. Do not enter real card details. Account registration and checkout are currently closed; this page will be updated when the test flow is ready.