FAQ

What is Buildspace?

Buildspace is a platform for shipping apps with the backend pieces already wired up well. Instead of stitching together auth, storage, databases, deployment, and environment config across multiple tools, you start with one platform that is designed to make those pieces work together.

How does Buildspace work?

Buildspace handles the infrastructure and service wiring around your app code.

• You build your product and UI however you want.
• Buildspace provisions the backend pieces your app needs.
• The platform injects credentials and environment config for you.
• Your app talks to Buildspace through one SDK for auth, events, storage, and notifications.

That means less setup glue, fewer dashboards to bounce between, and a faster path from idea to a working product.

Why does Buildspace work well?

Buildspace works well because the platform is designed as one cohesive system instead of a pile of separate integrations.

• The SDK is unified, so the same package covers multiple services.
• The services are provisioned with your app and environment in mind.
• Credentials and defaults are set up for you instead of copied around by hand.
• The platform is built for shipping, not just local setup.

In practice, that means you spend more time building product logic and less time wiring infrastructure together.

Why is Buildspace cohesive to use?

The core pieces are meant to reinforce each other.

• Auth can power access to the rest of your app.
• Storage, database, and runtime setup are tied to the same app environments.
• Creator Studio, deployment, and service configuration live in one workflow.
• The docs, SDK, and platform defaults all point in the same direction.

That cohesion matters because it reduces the usual edge cases that show up when every backend tool comes from a different vendor with a different setup model.

Do I have to use every Buildspace feature?

No. You can use the parts of Buildspace that help you and keep the rest of your app flexible. The goal is to give you strong defaults, not box you into a rigid app architecture.

Can I bring my own domain?

Custom domains are coming soon.

For now, Buildspace handles the default hosted setup so you can get running quickly.

Can I use my own database, like Supabase or Neon?

Yes. Buildspace makes it easy to get started with the managed database and storage setup provided by the platform, but your app code is still your app code.

If you want to plug in your own database, storage provider, or other backend tools, you can do that inside the app you build. Many teams will start with the Buildspace-managed defaults to move faster, then swap in or add their own infrastructure where it makes sense.

What database does Buildspace provide by default?

Buildspace provides a managed Turso database for each app environment and injects the connection credentials into your deployed service automatically.

See Database Overview and Database Setup.

What storage does Buildspace provide by default?

Buildspace includes managed storage so you can handle uploads, signed URLs, and file access without setting up that infrastructure from scratch.

See Storage Overview, Storage Client SDK, and Storage Server SDK.

Is Buildspace only for apps fully hosted on Buildspace?

No. The platform gives you a smooth default path, but the docs and SDK are intentionally developer-oriented. You can use the managed pieces that save you time and still make your own implementation choices inside the app.