Publish internal pages from developer workflows.
internalpage gives teams a private URL for generated reports, Markdown docs, OpenAPI references, previews, and operational pages without turning every artifact into a public static site.
What you can do
Publish a page source
Create a private page from HTML, Markdown, or an OpenAPI spec and share the viewer URL with your team.
Render Markdown and OpenAPI
Use GitHub-like Markdown rendering or a read-only Redoc API reference without running a portal.
Update the same page
Replace the latest version while keeping the same page ID and sharing path.
Use it in CI
Attach generated reports to pull requests, deploy checks, and release workflows.
Keep tokens scoped
Use personal API tokens for creator attribution and revoke them when workflows change.
Core model
internalpage is built around a small loop:
- Create a personal API token in your workspace.
- Publish an HTML, Markdown, or OpenAPI file with the CLI or API.
- Share the generated viewer URL.
- Update by page ID when your source changes.
Start here
- Quickstart: publish your first page.
- CLI reference: install and run
@internalpage/cli. - Page file types: publish HTML, Markdown, and OpenAPI files.
- API reference: authenticate and call the Pages API.
- Use cases: common developer workflows.