Drawing 001 — Docs · Community · Blog
Your knowledge, where every stream converges.
Forumulate runs your documentation, your community forum and your editorial blog on one managed platform — one account, one search, one identity.
Record
Linked docs
FIG. 01One workspace — the docs, the forum and the blog indexed together, sharing one identity.
Stop stitching a docs host, a forum, and a blog together.
Forumulate shares one login, one search index, one identity, and one permission model across all three surfaces. A member you invite, a role you grant, and a page you publish work everywhere.
Docs your team can change safely.
A structured editor, real versioning, and change requests with review rules — so nothing reaches readers unreviewed.
- Change requests with reviewers, merge rules & conflict resolution
- Space-wide version history and one-click restore
- OpenAPI references with a live test console
- Git round-trip sync, variables & reusable content
- Grounded AI answers over your published docs
Reviewers
Revision
FIG. 02A change request under review — two approvals, then it merges and publishes.
signing_key, then drop the old one.Output
FIG. 03The signature operation — a solved answer becomes a documentation page in one action.
A forum that feeds your documentation.
A full Discourse-style community — trust levels, badges, flags and moderation — with the signature move: promote a solved thread straight into your docs.
- Trust levels, badges & reputation that unlock privileges
- Typed flags, a reviewable queue & an AI spam classifier
- Categories, tags, tag groups & saved searches
- Real-time chat with threads, DMs & reactions
- Reply — and start topics — by email
Changelogs and stories, on the same stack.
Author, schedule and co-byline posts; publish a clean editorial reader with RSS — next to the docs and community they're about.
- Scheduled publishing and multiple authors
- Per-space RSS and a docs updates feed
- Newsletter signup with one-click unsubscribe
- Embed docs search or forum comments on any site
Distribution
Subscribers
FIG. 04Scheduled, then released to every channel at once.
A question becomes documentation.
Someone asks
A question is posted in the community — indexed from the first second.
The community answers
Promote to docs
Everywhere, instantly
FIG. 09Exploded assembly — one record, three layers
Nothing is ever lost, and git stays the source of truth.
Every space keeps its full history, and the repository round-trips: a commit becomes a page, an edit becomes a commit, and conflicts surface for review instead of overwriting someone.
FIG. 10Scrub the revision rail and restore any earlier state of a page.
FIG. 11Round-trip sync — commits in, edits back out, conflicts flagged.
Reference pages you can actually run.
Import an OpenAPI spec and every endpoint becomes a live console — parameters, auth, a real request and the real response, inside the docs.
- OpenAPI 3 import with schemas, auth & examples
- Executable requests against your own environment
- Generated SDK and CLI from the same specification
- Scoped API tokens with per-token audit
FIG. 12Send a request from the reference and read the response in place.
One query, every surface, filtered by what you may see.
Lexical and semantic retrieval run together and fuse into a single ranking — then the result set is cut down to exactly what the reader has permission to open.
FIG. 05The reader’s view — records from docs, forum and blog in one index.
FIG. 13The mechanism — tokenise, BM25 and vector search, fuse, then rank.
FIG. 14Retrieved passages are cited inline — the answer is traceable to records.
Answers that cite the record they came from.
The assistant only reads what you have published and what the asker is allowed to see. Every claim carries a citation back to the page or thread it came from.
- Retrieval scoped to the reader’s permissions
- Inline citations back to docs, threads and posts
- Draft pages and translations from your own content
- Bring your own model key, or use ours
Reputation that maps to real permissions.
Members advance through trust levels by participating, and each level unlocks concrete privileges — up to promoting an answer into the documentation.
FIG. 06One member record — trust earned anywhere applies everywhere.
FIG. 15The state machine — transition conditions and what each level unlocks.
Only the uncertain middle reaches a human.
Every post is scored on arrival. Clear spam is rejected, clean posts publish, and the ambiguous band goes to a prioritized review queue with the evidence attached.
- Typed flags with a reviewable, prioritized queue
- Automatic actions by score threshold
- Rate limits, silences and a full audit trail
- Watched words, spam checks and new-user limits
FIG. 16A post is scored, then routed to allow, queue, or reject.
One permission model, wired to your directory.
Capabilities are granted through roles, roles can be granted to whole groups, and your identity provider keeps membership current without anyone filing a ticket.
FIG. 17Roles × capabilities — a group grant applies to every member at once.
FIG. 18SAML sign-in with SCIM provisioning and deprovisioning.
A platform you can build on, not just configure.
Signed webhooks with retries and replay, a documented REST API, and remote-app extensions that register their own blocks and surfaces without forking anything.
FIG. 19Delivery with backoff — a failed event is replayed from the log.
FIG. 20An extension seats into a surface socket and registers its parts.
Instrumented, and answerable after the fact.
Prometheus metrics and structured logs from day one, plus an immutable audit log that records who changed what — the things you need when something goes wrong at 3am.
FIG. 21Request rate and p95 latency, with the audit trail beneath.
One Forumulate, or three separate tools.
A docs host, a forum, and a blog platform each solve one slice — and none of them talk to each other.
Run by us, so you never have to run it.
Monitored around the clock, backed up nightly, and patched before you hear about the CVE. Enterprise identity is built in — and your data stays exportable, so staying is a choice rather than a trap.
Uptime & monitoring
Watched around the clock, with public status and incident history.
Backups & restore
Nightly automated backups, with point-in-time restore on request.
SSO, SAML & SCIM
Enterprise login and directory sync, per organization.
Org-wide MFA
Require two-factor across every member before they’re in.
Roles & audit
Custom roles, group grants, and an immutable audit log.
Portable data
Import from GitBook & Discourse; export everything, anytime.
FIG. 07Live platform status — uptime, backups and the last deploy.
Bring your docs and community with you.
Import from where you are today — structure, history and members intact — and keep every existing URL working.
FIG. 08A live import — counts and redirects tracked per source.
Import from GitBook
Pull your spaces, pages and structure into Forumulate docs — then keep git-syncing.
Import from Discourse
Bring categories, topics, posts and members into your Forumulate community.
Everything included, nothing bolted on.
Run for you, not by you
Monitored around the clock, backed up nightly and kept patched. Import from GitBook & Discourse, and export everything whenever you want.
One query, grounded answers
Full-text and semantic search across every surface, plus AI answers, page drafts and translation scoped to what you publish.
SSO, SAML & SCIM
Enterprise login, directory sync, org-wide MFA.
Roles & group grants
A capability model, custom roles, and roles granted to whole groups.
Observability built in
Structured logs, Prometheus metrics, scoped API tokens, webhooks & audit.
A platform, not a silo
A remote-app extension marketplace, a documented REST API with a publishable SDK & CLI, replayable webhooks, and embeddable widgets you drop on any site.
i18n & translation
Localized content and a translated admin UI.
One base, four jobs it does exceptionally.
Developer docs & API reference
Versioned guides and OpenAPI references with a live test console, git-synced and AI-answerable.
Support & Q&A community
A place customers help each other — trust levels, solved answers, and moderation that scales.
Product knowledge base
Internal or public knowledge that stays accurate, with change requests and an agent that reviews edits.
Open-source project home
Docs, discussions and a changelog under one roof — hosted for you, and yours to shape.
Good to know.
Issued for construction
Bring your streams together.
Spin up docs, a community and a blog in minutes — free to start, and we run it for you.