Prosefly
All comparisons
ProseflyKeystatic

Prosefly vs Keystatic

A shared workspace, or a CMS configured in your codebase?

Both work with content files. Keystatic brings a configurable admin UI into your project; Prosefly gives your team a hosted workspace connected to an existing repository.

Compare the details

Decide where the editor should live.

Keystatic lets developers define collections, singletons, and fields in code. Prosefly organizes supported repository content into Spaces and Collections, with writing and publication handled in the workspace.

Two ways to work with content.

Prosefly

A hosted writing workspace for an existing Git website.

  1. 01

    Connect a GitHub repository and choose a Space.

  2. 02

    Write together; save drafts in your workspace.

  3. 03

    Review the diff, then publish a commit or pull request.

Keystatic

A configurable content editor that reads and writes local or GitHub files.

  1. 01

    Define collections and fields in keystatic.config.ts.

  2. 02

    Edit using local, GitHub, or Keystatic Cloud storage mode.

  3. 03

    Render the saved files with your website.

A summary of each content workflow. Configuration and optional services can change the details.

A visual editor that understands your docs.

Start with visual Markdown and MDX editing. Dedicated support for Starlight, Fumadocs, and Prosefly components lets you work with supported documentation blocks in the same editor.

  • Starlight

    Edit asides, tabs, cards, and file trees, with support for Starlight component syntax and Expressive Code metadata.

  • Fumadocs

    Work with callouts, tabs, steps, and accordions using their Fumadocs component syntax and supported properties.

  • Prosefly components

    Edit callouts, tabs, cards, and accordions from @prosefly/astro-components, used by Lotus and Dahlia.

Support follows the Collection’s editor profile and the component syntax it recognizes. Custom components and unsupported expressions remain available in Source; repository code is not executed.

Explore visual editing

What changes in your day-to-day work.

Published content
Prosefly

Published Markdown and MDX in your Git repository.

Keystatic

Files in a local directory or GitHub repository, depending on storage mode.

Getting started
Prosefly

Connect GitHub, scan supported content, and configure a Space.

Keystatic

Install an integration and define keystatic.config.ts.

Editing experience
Prosefly

Visual and source editing, frontmatter properties, and real-time collaboration. Dedicated visual editing support for Starlight, Fumadocs, and @prosefly/astro-components.

Keystatic

Schema-defined fields and rich text, including Markdoc and MDX fields.

Drafts & saving
Prosefly

Draft saving never commits Git. Drafts stay in the workspace.

Keystatic

Local file saves or GitHub-backed editing, according to storage mode.

Publishing
Prosefly

Review file changes, then publish a commit or pull request.

Keystatic

Save content files; use the project’s Git and website workflow.

Media
Prosefly

Uploaded images, audio, and video stay separate from published text and are referenced by URL.

Keystatic

Configure image fields; Cloud mode offers image hosting features.

Hosting & maintenance
Prosefly

Prosefly hosts the workspace. You maintain your website and its build pipeline.

Keystatic

Maintain the project integration; Keystatic Cloud provides optional services.

Git publication does not deploy your site. Prosefly relies on your existing build pipeline, and repository refreshes require an explicit scan.

Keystatic’s MDX field has documented limits, including imports and HTML tags. Prosefly does not execute repository code; source editing and visual editing have different scopes. Check representative MDX files before choosing either editor.

Choose around the work you need to do.

Choose Prosefly when

  • Your website already uses Markdown or MDX.
  • You use Starlight, Fumadocs, or @prosefly/astro-components and want visual editing for supported documentation components.
  • Your team wants real-time writing and a separate draft workspace.
  • You want to keep your site builder and deployment pipeline.

Consider Keystatic when

  • You want a CMS integrated into your Astro, Next.js, or Remix project.
  • You want local file editing as well as GitHub storage.
  • You prefer defining custom fields and content components in TypeScript.

Take a closer look

Sources & scope

Reviewed

Product facts were checked against the official documents below. The choice guidance is our assessment. Optional integrations and paid editions may add capabilities; check the current documentation and terms before choosing.

Other comparisons

Keep your website. Make room for writing.

Connect your repository and try the workflow with your own content.

Try ProseflyRead the quickstart