Daptin

Home / Product / RSS, Atom, and JSON feeds

Publish to familiar readers

Let people follow changing product data in the reader they already use.

Turn a configured stream of application records into a standard feed for updates, catalogues, releases, or public activity.

See what it changesTechnical guide ↗
01Meet people outside your UIPublish updates to feed readers and aggregators.
02Reuse live product recordsBuild the feed from the same data behind your application.
03Offer standards instead of lock-inUse familiar formats that many clients already understand.
Why it matters

Not every useful product experience needs another app screen or notification channel.

Readers may want new articles in their feed reader. Partners may want a catalogue update. An operations team may subscribe to a public change stream. Building a custom client for each audience adds friction.

Daptin can turn configured record streams into RSS, Atom, or JSON feed output. The feed remains grounded in application data and can sit beside the APIs, sites, and actions that create those records.

This extends the product through established formats and gives people a low-friction way to follow information without learning a Daptin-specific client.

01

Reach existing habits

Let people subscribe with the reader or aggregator they already trust.

02

Publish once from the application

Avoid copying updates into a separate feed-only content store.

03

Support several clients

Offer common feed formats from one configured source.

How it fits

Part of one connected backend.

RSS, Atom, and JSON feeds does more when it can reuse the records, people, access rules, and workflows already in your application.

Step 1Select

Choose the application data that represents the update stream.

Step 2Shape

Define ordering and presentation for the feed.

Step 3Publish

Serve RSS, Atom, or JSON output.

Step 4Subscribe

Existing clients retrieve new entries on their own schedule.

What it enables

Use it in products people recognize.

Start from the experience you want to create; the backend capability supports the work behind it.

Product updates

Publish releases, changelog entries, or announcements.

Content publication

Let readers follow a blog, knowledge base, or newsroom.

Public catalogue

Expose new listings or opportunities to aggregators.

Connected by design

Build the next part without starting over.

These capabilities share the same application context, so each one makes rss, atom, and json feeds more useful.

Works better together

Data models

Give every feed entry a structured source record.

Explore Data models →Works better together

Sites

Publish the human-facing experience beside its subscription feed.

Explore Sites →Works better together

Templates and responses

Shape readable titles, summaries, and links from current data.

Explore Templates and responses →
Know the boundary

What Daptin leaves in your hands.

Feeds are pull-based publication, not realtime push or guaranteed delivery. Choose public data carefully, provide stable links, plan caching and update frequency, and test the exact clients you expect people to use.

Understand the operating responsibility →

Build from one foundation

Make rss, atom, and json feeds part of the product—not another disconnected service.

Run Daptin locally, explore the live administration surface, and follow one complete application path.

Get DaptinExplore all capabilities