BaseHub

1. Speed & Collaboration: The experience in the web apps is too slow and single-player.
2. Editing Experience: There’s one place to model content and a separate one to actually create it.
3. Developer Experience: The APIs are not straightforward nor type-safe.
4. Content Workflow: The editing workflow is too basic; for example, there’s usually no way for an editor to create their own version of a document without compromising production content.

Diff View

The Diff View is a powerful way to see all the changes you've made across your whole Repo, so you can Commit them with confidence.

Docs

We shipped our Docs, one place in which you can get to know the Platform. We'll work hard to explain concepts in a simple manner, and add guides and examples for you to connect BaseHub to popular web frameworks. You can check out our guide for connecting to Next.js to get a hang of how our DX is!

Billing

We've built the Billing infrastructure that will let us provide the service sustainably. Now Teams can pay for BaseHub, and our pricing plans are as it follows:

• Personal Account, starts completely for free, and includes:
  • One user, you
  • Discord Support
  • AI Assistant
  • 375 Blocks, then $2.5 per 125
  • 75k API Requests, then $2.5 per 25k
• Team, starts at $29, and includes:
  • Unlimited users—bring your whole team to BaseHub
  • Discord + Email Priority Support
  • AI Assistant
  • 500 Blocks, then $2.5 per 125
  • 100k API Requests, then $2.5 per 25k

Mission

Our mission is to be the place where people create, store, and deliver great content for the Internet.

To that end, we’re building a tool that lets you write structured content fast, in a beautiful, snappy, collaborative webapp. It leverages AI to speed up your workflow. Most importantly, we’re building a versioning system similar in properties to git: changes are stored in immutable snapshots (“commits”), and a linear history is preserved.

This architecture decision might seem trivial, but enables powerful collaboration workflows, such as branching, merging, diffing, and eventually “Content Requests” (ode to GitHub’s “Pull Requests”), forks, and more. We’re building git for structured content. We see this as the missing piece of the content story in the Web.