Skip to main content
kombify Sites lets you create and publish a website, a slide deck or a topic artifact. The hosted product maps these to the web, deck and topic-artifact site types. The experimental app type is not offered for hosted sites. Sites is in beta; version 1.0 has not been released.

Editing and usage

Your account’s Sites entitlement and the available service capacity govern site creation and usage. The service checks that entitlement before persistent owner work. A visitor’s conversation with a published site does not give the visitor permission to edit its owner’s source. See plans and billing for Cloud subscriptions. Owner editing supports published, source-built websites and published decks with available or migratable deck source. It does not support topic artifacts. Source snapshots for these edits are limited to 200 files and 2 MB. For websites, the serialized source-file data passed to the model is limited to 180,000 characters; encoded binary files count toward that limit. For decks, the same limit applies to serialized slide data. A preview does not publish the edit. Publishing requires the site to remain at the revision on which the preview was based.

Export and portability

The dashboard offers GitHub export for a published site backed by Cloudflare Artifacts and an active publishing entitlement. It requires a GitHub HTTPS repository address and a token with permission to write to that repository. Use a fine-grained token limited to the target repository with Contents write access. The export pushes the live revision, or the last unpublished revision if there is no live revision, to main. It is a normal push: use an empty repository or one whose main can accept that history. Later commits are not synchronized. kombify removes the temporary sandbox containing the token after the export. The source archive download is not available yet. The authenticated owner can use the Sites API to request a short-lived read token for an Artifacts source repository, or access the last live R2 source snapshot and its files when one exists. These API paths check site ownership and do not require an active publishing entitlement; they do not currently have a dashboard screen. Treat the read token as a secret. It expires after one hour by default and its lifetime can be configured by the service. The owner API routes are GET /sites/:slug/source-token for Artifacts and GET /sites/:slug/source-snapshot and GET /sites/:slug/source-snapshot/file for R2 snapshots. The file route takes a path query parameter. All routes require an authenticated owner session. Unpublishing takes a site offline while keeping its source and revisions. Site deletion attempts to remove its source and published artifacts and reports any failed steps. Account erasure also removes retained source snapshots. Export what you need before deletion. Source export does not transfer hosted domains, account settings, usage allowances or service integrations to another host. Running a site elsewhere requires a compatible host and any services the site uses. Decks offer a browser print-to-PDF action. The browser and its print settings determine the resulting PDF.