Short answer: A static export is a set of files with no runtime dependency and no platform lock-in; a hosted docs platform owns the hosting and the configuration. The first is reversible; the second is a relationship. For a reference that should outlive any vendor decision, the export is the safer form.
What a platform accumulates
Configuration, content conventions, and a dependency on the hosting. These are convenient while the relationship is good and expensive to unwind.
What a static export keeps
| Property | Platform | Static export |
|---|---|---|
| Runtime | The platform | None |
| Hosting | Managed | Anywhere |
| Configuration | Platform-specific | Plain files |
| Exit cost | Migration | Minimal |
Why the runtime matters
A static reference has no service to keep running, so it cannot be affected by a vendor outage or a pricing change. It is the most durable form for a reference.
The honest tradeoff
The platform gives you the hosting and the broader product. The export gives you portability and asks you to handle the hosting yourself.
This is part of the Powerduck vs Mintlify comparison. Finish with code samples.
Comments
Join the discussionNo comments yet. Be the first to comment.