Fornace Create
Guides

Short guides for everything you can do here.

From your first prompt to your first tip jar: quick reads with the exact steps for building, publishing, domains, credits, and secrets.

Home
Guides

Short guides for everything you can do here.

From your first prompt to your first live link: each guide is a quick read with the exact steps. Pick a topic and go build.

Building your first appStart here

You describe what you want, the agent builds it, and you watch it take shape in a live preview. The best first prompts say what the app does, who it is for, and roughly how it should feel. Iterating is just replying, one clear change at a time.

  1. Hit New creation and describe your app in one or two plain sentences.
  2. Watch the preview panel build as the agent works.
  3. Reply with one change at a time, like "make the timer gold and huge".
  4. Say what you want, never "improve it": name the exact change.
  5. Publish when it feels right, and keep iterating after if you like.

Publishing and sharingShare

Publishing gives your app a public address that anyone can open, no account needed. You choose the app name when you publish it. You pick the slug, so the link can read like a name. Published apps can also show up in Discover, where people browsing the gallery will find them.

  1. Open the publish flow from your creation.
  2. Pick a slug: it becomes the public address of your app.
  3. Confirm the publish and wait for it to go live.
  4. Share the direct link anywhere, chats, posters, bios.
  5. Opt in to Discover to let the gallery surface it.

Custom domainsYour name

A custom domain puts your creation on an address you own, like app.yourbrand.com. You point your DNS at Fornace, we verify it, and the domain serves your published app. Custom domains use slots from your plan.

  1. Open your published creation and choose the domain option.
  2. Enter the domain you want to use.
  3. Add the DNS records we show you at your registrar.
  4. Wait for DNS to spread, then verify and go live.

Credits and pricingFuel

Building runs on compute credits: every build, edit, and agent action spends a little. Your plan grants a monthly allowance, you can top up any time from Plans, and support from your fans can add credits too. Sleeping apps cost nothing.

  1. Check your balance and usage inside the Plans panel.
  2. Build and iterate: each agent action draws down credits.
  3. Top up from Plans when your runway gets short.
  4. Pick a bigger plan for a larger monthly allowance.
  5. Earn bonus credits by completing your profile and first publish.

Keeping creations awakeUptime

Free creations rest after a stretch without visitors, because an idle app still costs compute. Anyone opening the link wakes it back up in moments. Support from fans and always-on slots keep an app online around the clock instead.

  1. Know the deal: free creations sleep when quiet, and wake on the first visit.
  2. Share the link so visitors keep it warm.
  3. Let fans support it: their tips fund awake hours.
  4. Use an always-on slot or a paid plan for nonstop uptime.

Fan support is being shapedPreview

We are designing a simple way for fans to help fund a creator’s app. Today, every published creation gets a shareable link, and free apps can be woken with one click. Direct fan funding is still a product direction.

  1. Publish and share your creation today.
  2. Visitors can wake a resting free app with one click.
  3. Treat support examples on this site as illustrations.
  4. We will document the live flow here when it is ready.

Connecting GitHubCode

Save a GitHub token as a secret and the agent can read and update your repositories on your behalf. The token stays on the server: it never reaches the chat, the sandbox, or the transcript. The agent asks before it pushes anything.

  1. Create a token on GitHub with repo access.
  2. Save it as a secret in Settings, for example GITHUB_TOKEN.
  3. Ask the agent to read or update one of your repos.
  4. Approve writes when the agent asks, and review the result.

Secrets and provider keysKeys

Provider keys, like API tokens for email or payments, live in Settings under Secrets. Values are encrypted at rest and are never shown to the agent, the sandbox, or anyone browsing. When a build genuinely needs a key, the agent pauses and asks you through a prompt, and your answer is injected without ever appearing in plain text.

  1. Open Settings and add your key as a named secret.
  2. The value is encrypted immediately and stored for you only.
  3. The agent never sees the raw value, in chat or in the sandbox.
  4. When a build needs it, the agent asks, you reply, and it is wired in quietly.
  5. Published apps receive secrets as environment variables, never as visible files.

Ready to try one of these for real?