Prosefly
All comparisons
ProseflyPayload

Prosefly vs Payload

A writing workspace, or a backend you build and run?

Prosefly connects writers to an existing Git website. Payload gives developers a configurable backend with a database, admin UI, access control, and APIs.

Compare the details

Choose the responsibility you want to take on.

Payload is useful when content belongs inside a larger application with custom data, permissions, and business logic. Prosefly focuses on the writing workflow for supported Markdown and MDX websites, with a hosted workspace and Git publication.

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.

Payload

An open-source backend with an admin panel, database, and content APIs.

  1. 01

    Define a Payload Config, collections, and a database adapter.

  2. 02

    Edit content and configured drafts in the admin panel.

  3. 03

    Read published content through Payload’s APIs or your application backend.

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.

Payload

Records in the database configured for your Payload application.

Getting started
Prosefly

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

Payload

Define a Payload Config and configure a database adapter.

Editing experience
Prosefly

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

Payload

Generated admin panel, custom fields, and application integrations.

Drafts & saving
Prosefly

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

Payload

Optional drafts and autosave are configured per collection or global.

Publishing
Prosefly

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

Payload

Publish records and consume them through REST, GraphQL, or local APIs.

Media
Prosefly

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

Payload

Upload collections with configured file storage and optional storage adapters.

Hosting & maintenance
Prosefly

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

Payload

Deploy and maintain the application, database, and storage, or choose managed hosting.

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

Payload’s code and database can be owned and hosted by you. The distinction is repository files versus database records, not ownership versus lock-in. Prosefly is not a general application backend and does not automatically migrate Payload collections.

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 Payload when

  • You need custom backend logic as well as content editing.
  • You want direct control over hosting, database, and access rules.
  • You want to integrate content with a Next.js application.

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