Visual and source editing
Work with Markdown and MDX in the visual editor, or open the complete source. Edit frontmatter properties alongside the document.
Explore editingEdit Markdown and MDX with your team, review the changes, and publish directly to your website’s Git repository.
One calendar-month Personal trial for eligible new accounts.
Your content lives in your Git repository.
An editor for writers, with Markdown and MDX underneath. Work together, manage your media, and keep using the website you already have.
Work with Markdown and MDX in the visual editor, or open the complete source. Edit frontmatter properties alongside the document.
Explore editingCollaborate in real time, give each person the right role, and follow changes through organization activity.
Explore collaborationArrange pages and groups with supported native navigation. Review content and navigation changes together before publishing.
Explore SpacesReuse images, upload audio and video, and see audio/video analytics in the same workspace.
Explore mediaReview the actual file changes before publishing. Choose a commit or pull request, and follow the result in publish history.
Read the publishing guideAuthorize GitHub, choose a repository, and scan its content.
Choose a Space and Collection for your docs, articles, or other content.
Edit visually or in source, manage properties, and collaborate in real time.
Inspect the diff, then publish a commit or pull request. Your existing site build takes it from there.
Published content stays alongside your website’s source code. Prosefly helps your team work on it, while Git keeps the files and their history.
How content ownership works---
title: Hello, world
date: 2026-10-08
---
# A little room to write.
Your next story starts here.Published as a normal file in your repository
Markdown and MDX files stay in your repository, with their existing paths and frontmatter.
Review changes as a diff, publish a commit, or open a pull request for your team.
Keep using your code editor and compatible site builder with your published files.
Drafts stay in your workspace. Only publishing writes to Git.
CMSs such as Sanity and Payload typically store content in a CMS-managed data store and deliver it through APIs. Prosefly writes published content back to your own Git repository.
One workspace for your guides, stories, and episodes. The files stay part of your website.
Let writers and developers improve guides together, with review in Git.
Explore documentationWrite articles, manage frontmatter, and keep your existing publishing stack.
Explore writingManage episode copy alongside audio, video, and delivery analytics.
Explore podcast contentPublished content is stored as files in your GitHub repository. Drafts and collaborative editing state are saved in Prosefly until you publish. Media uploads are managed separately and referenced by URL.
No. Saving a draft only saves it in your workspace. Git changes happen when you explicitly publish a commit or pull request.
Your website keeps its existing framework and build process. Prosefly edits and publishes the content files. A Git publication does not itself deploy your website.
Yes. Your published files remain normal repository files. After external Git changes, scan the repository to refresh the workspace. If the Git version changed while you had a draft, review the conflict before publishing.
There is no permanent Free plan. Eligible new accounts receive one calendar-month Personal trial when creating their first organization. Paid plans are Personal, Team, and Business.
Give your team a place to write, with your website and Git workflow already in place.
Start writingRead the quickstart