A content backend you won't have to babysit
Typed content reads that fail at build time, forms without a backend, an MCP server in every workspace, and one-command hosting in beta. One platform to run the site after it is built, whether you built it or someone built it for you.
Free tier. No credit card.
// src/content.config.ts
// No package to install.
import {
defineCollection,
z,
} from 'astro:content'
// ~15 lines of fetch.
// Recipe in the docs.
import { sedgemarkLoader } from './sedgemark'
const blog = defineCollection({
loader: sedgemarkLoader('blog_post'),
schema: z.object({
title: z.string(),
body: z.string(),
}),
})
export const collections = { blog }No adapter to install, just fetch. Any static site generator via the HTTP API.
What you skip building
Less infrastructure to build and babysit
The parts of a content stack you would otherwise assemble yourself, already running and isolated per workspace.
Types
Breaks at build time, not in production
A generated TypeScript client and an Astro content-layer loader, typed to your exact schema. Rename a field the site still reads and the build stops.
Forms
Forms without a backend
Allowlist your site’s origin, point the form at the endpoint, and you are done. Validation, anti-spam and CSV export run on the server, so there is no function to deploy and nothing to watch.
Forms come with Pro and up.
Infrastructure
An isolated workspace per project
Own database, own keys, own subdomain. Media API, webhooks and per-resource API keys included. None of it is yours to maintain.
Delivery
Static output, fast by default
The read API serves published content only, so drafts stay separate. Your site builds to static files, so nothing happens at request time.
MCP & agent tooling
Point the agent you already use at it
Every workspace ships an MCP server over streamable HTTP, nothing to install. On connect, the agent is briefed on your collections and the grants its key holds, so it never has to guess at your setup.
describe_api
Returns the live API contract as structured data: base URL, auth, pagination, media URLs.
get_client
Returns a TypeScript client generated for your exact schema, in one tool call.
sedgemark://guide
A resource carrying the full integration guide, framework recipes included.
entries:write
Every tool (reads included) is gated on the grants its key holds. You tick the boxes, so you pick what the agent can do.
claude mcp add sedgemark --transport http \
https://acme.sedgemark.app/api/mcp \
--header "Authorization: Bearer $SEDGEMARK_API_KEY"You don't have to be deeply technical to run Sedgemark behind an Astro site. Point your agent at your workspace and it wires things up correctly. The docs are written to be agent-readable too. MCP server docs
Coming next
Content is the first piece
The same workspace is where the rest of running a site is heading. Names and timing may shift as these ship.
Content
Typed content, forms, media and an MCP server per workspace.
Hosting
One command to deploy the site, served from the same place. Pro and up, per-workspace beta.
Commerce
Products, checkout and orders in the workspace you already have.
Sedgemark Build
Not going to build it yourself?
For owners who are not building the site themselves and do not want an agency retainer: we build it once for a one-time project fee and hand over the workspace. From there, you run it here like any other site.
Start with the free tier
Create a workspace, mint a key, and read your content over HTTP a few minutes later. No credit card.
We never meter API requests. No overage charges, no hard cutoffs, on any plan, ever.
Not ready yet? We will email you when there is something new, nothing else ever.