Skip to main content

Fully Managed oPodSync
as a Service

Deploy oPodSync as a fully managed service starting at €9/mo. Get automated backups, SSL, updates, support and monitoring included.

oPodSync is a lightweight self-hosted podcast subscription sync server that speaks the gpodder.net API — subscriptions, episode actions, device sync — combining the convenience of a centralised tracker with the privacy and control of running your own instance.

Free 7-day trial  99.9% Uptime SLA  No credit card  Cancel anytime

Free 7-day trial  99.9% Uptime SLA
No credit card  Cancel anytime

oPodSync

oPodSync

STARTING AT

€9/month
Automated Backups
Monitoring
Automated Updates
Auto SSL

USAGE

Unlimited
Human Support
Custom Domains
Terminal Access
File Manager Access
Deploy in your region 21 locations worldwide
GermanyFinlandNetherlandsUKSwedenUnited StatesCanadaSingaporeJapanAustraliaBrazilSouth Africa+9 more →
oPodSync Preview Image

ABOUT THE SOFTWARE

What is oPodSync

 oPodSync is a minimalist PHP and SQLite server that implements the gpodder.net synchronisation API. Any gpodder-compatible podcast client can talk to it — AntennaPod, gPodder desktop, Kasts, PinePods, Music Assistant, Podliner — without modification or shims.

The project was published in August 2022 by BohwaZ at kd2.org and is licensed under the GNU AGPL version 3. The canonical repository is hosted on Fossil at fossil.kd2.org with a mirror on GitHub for pull requests.

The install footprint is one PHP directory and a single SQLite file. Tested community Docker deployments cap memory at 500 MB and a quarter of one CPU core. Authentication runs against an internal account table or, for institutional deployments, a reverse-proxy HTTP_REMOTE_USER. The server implements the full gpodder.net API surface except one episode-updates endpoint, plus the NextCloud GPodder Sync app endpoints that newer AntennaPod builds prefer.

FEATURES

What oPodSync does

 oPodSync exposes the subset of the gpodder.net API that real clients exercise. The point is not a complete API museum — it is that AntennaPod, gPodder, Kasts and PinePods talk to it without code changes. 

gpodder.net API compatibility

Implements the GPodder authentication, episode actions, subscriptions, devices and device-sync endpoints in JSON. Any gpodder-aware client connects to a DANIAN URL without modification.

Cross-device episode-action history

Records plays, pauses, downloads, deletions per device and per user. Resume position on a phone matches resume position on a desktop within one sync cycle.

Optional feed-metadata fetching

From v0.3.0 the server fetches and stores podcast feed titles, descriptions and website URLs on an hourly cron. The web UI shows show names even when clients do not push metadata.

Multi-client coverage

Tested with AntennaPod on Android, gPodder desktop, Kasts on KDE Plasma, PinePods as a web client, Music Assistant via its gPodder provider, and Podliner in a terminal.

NextCloud gPodder Sync API parity

Speaks the endpoints from the NextCloud GPodder Sync app as well, so AntennaPod builds that prefer the NextCloud flavour connect without shims or compatibility layers.

Subscription sync with OPML

Exports your subscription list at /subscriptions/(username).opml and accepts text or OPML uploads per-device. Migration off gpodder.net or onto a new client is one file.

Minimalist PHP and SQLite footprint

Runs on PHP with SQLite and the JSON1 extension. Tested community deployments stay under 500 MB of memory and a quarter of one CPU core in normal use.

KaraDAV-compatible deployment

Can run inside KaraDAV, BohwaZ's NextCloud-protocol WebDAV server, presenting oPodSync alongside calendars, contacts and files via NextCloud-style endpoints on one host.

WHAT'S ALWAYS INCLUDED

Every app. Fully managed.
Nothing extra to pay for.

Every app you deploy includes the full managed service — security, backups, updates, and support from day one.

Automatic updates and patches

Apps run the latest stable version. Security patches applied silently, with rollback if needed.

Daily off-site backups

Multiple daily backups in redundant off-site locations. One-click restore if anything goes wrong.

24/7 uptime monitoring

Continuous monitoring with instant alerting. We respond before you notice.

SSL, firewall, DDoS protection

Auto-renewing SSL, hardened firewall rules, DDoS mitigation on every deployment.

Performance and scaling

We monitor resource usage continuously. When your app needs more headroom, we flag it and upgrade with your explicit approval.

Dedicated engineering support

Real engineers on chat. DNS, SMTP & migration help. All included in €9.

WHY MANAGED

Why teams pick managed oPodSync

Through 2024 and 2025 gpodder.net moved from "often overloaded" to active archival of inactive accounts, with DB migration completed in June 2025 and archives kept at least until 30 June 2026. AntennaPod's documentation now explicitly tells users to self-host a sync server.

Running oPodSync yourself is straightforward in the install sense — drop one directory into a webroot, point a domain at it, paste the .htaccess rules into your config. The operational work that "just running oPodSync" does not include is the work that keeps it reliable for the year after install: applying patch releases to a server that podcast clients now poll on a schedule, watching the SQLite file under concurrent device sync, keeping the Authorization header passthrough working when the upstream README marks Caddy and nginx as untested.

One specific failure mode is worth naming. AntennaPod issue 7453, filed in October 2024 against an oPodSync deployment, reported episode-action timestamps off by exactly the device's timezone offset — phones in Spain producing UTC times that were two hours wrong. The fix is server-side: pin the PHP timezone to UTC. A self-host who never sees the issue tracker never finds out why their play history looks confused across daylight-saving transitions.

REVIEWS

Hear from customers ​like you​​​​​​​

Successful businesses and professionals around the world rely on DANIAN every day

USE CASES

Three teams who run oPodSync on DANIAN

These are representative team types we set up most often. Each starts with the same flat €9 plan.

MULTI-DEVICE HOUSEHOLD

Replacing gpodder.net for a family on AntennaPod and Kasts

Two adults, four Android phones, one Linux desktop, one KDE laptop, about eighty subscriptions between them. Hit gpodder.net 500-errors weekly through 2024. Now sync against a Germany instance with shared resume points across AntennaPod, Kasts on KDE, and Music Assistant in the home automation stack. 

INDEPENDENT PODCAST STUDIO

Four editors, 120 research subscriptions, off centralised trackers

Two weekly shows, four editors tracking what competitors and adjacent creators publish. Subscription lists kept private for competitive reasons. Self-registration off after provisioning, OPML exports automated nightly to internal Drive, eight active device IDs against one SQLite file. 

INVESTIGATIVE JOURNALIST

800 subscriptions across five devices, no centralised log

A journalist tracking investigative, policy and tech beats refuses centralised trackers because subscription lists reveal sources. AntennaPod on two phones, gPodder desktop, Kasts on a tablet, Podliner on a server. The 800-feed OPML import is the stress test the WAL tuning was designed for. 

COMPARISON

Four ways to run oPodSync

 The honest comparison is unusual: the centralised free option is contracting, the closest paid app locks you to one client, and self-hosting works but trades money for hours. The numbers below come from each provider's current public pricing. 

 PATH1 USER5 USERS 10 USERSWHAT YOU ACTUALLY GET
Proprietary SaaS
Pocket Casts Plus, annual
$39.99/yr$199.95/yr$399.90/yrCross-device sync inside one closed client. No third-party podcast app can read it.
gpodder.net
Free centralised service
$0$0$0Inactive accounts archived since June 2025. AntennaPod recommends self-hosting instead.
Self-host on a VPS
$24/mo production-class VPS
$288/yr + time$288/yr + time$288/yr + timeYou patch PHP, debug reverse-proxy auth, monitor SQLite locking, run backups.
DANIAN Managed oPodSync€9/mo€9/mo€9/moOne instance, any number of accounts and devices, AntennaPod and gPodder desktop tested.

BY INDUSTRY

oPodSync for specific industries

 Podcasts are a primary information channel for several professions where central sync services do not fit — for source-protection reasons in journalism, for data-minimisation reasons in education, for accessibility reasons in disability services. 

The IFJ Declaration of Principles on the Conduct of Journalists, Article 6, makes protecting confidential sources a professional duty. Centralised podcast-sync services log every subscription and every play, by user, against an IP address. For an investigative desk that subscribes to whistleblower-friendly shows or beat-specific feeds, the subscription list is the source list.

On a DANIAN oPodSync instance we disable self-registration after provisioning, enforce HTTPS-only, turn off user-triggered feed metadata fetches so the server is not observed pulling feeds at predictable intervals from a known IP, and run daily off-site encrypted SQLite backups. A six-person desk with two device IDs each — phone and laptop — is about twelve device IDs and a database that typically stays under fifty megabytes. 
GDPR Article 5(1)(c) requires data minimisation: an institution cannot lawfully send student listening history to a third-party podcast sync service that retains it indefinitely. Most institutional IT policies independently forbid student data leaving the institution. The two pressures converge on self-hosting.

We support reverse-proxy SSO via HTTP_REMOTE_USER so students log in with the institution's identity provider, keep self-registration off, and prune episode actions on a 90-day rolling window. A media-studies module of forty students sharing a curated OPML of thirty podcasts runs comfortably on a single SQLite instance, with the lecturer reading engagement counts in the oPodSync web UI without the data ever touching a SaaS. 
EN 301 549 and WCAG 2.2 §1.4 establish accessibility as a procurement requirement across the EU and the UK. Podcasts are a primary information channel for blind and low-vision users, and AntennaPod is one of the most widely used screen-reader-friendly podcast clients in this population — its Android download volume sits above one million per the Play Store and AppBrain.

We pre-load OPML starter packs into the oPodSync instance during provisioning, support shared device records per member so a member can switch between a phone and a tablet without re-subscribing, and keep the deployment HTTPS-only. A national charity supporting up to five hundred member accounts on one instance, with a monthly twenty-to-fifty-show OPML refresh from the programme coordinator, is a normal workload. 

FAQ

Frequently asked questions

Everything teams ask before signing up — answered straight, without sales speak.

Three groups: technical setup, migration, and how DANIAN works as a service.

01

Technical and configuration

Almost always the gPodder desktop secret-token has been pasted into the AntennaPod password field, or the reverse. AntennaPod uses the real account password. gPodder desktop cannot send HTTP Basic auth at all — a long-standing upstream gPodder bug — so its login takes the secret token as the username instead. We surface both values separately in the dashboard so the right one ends up in the right field.
This was reported as AntennaPod issue 7453 in October 2024. AntennaPod was uploading timestamps in the device local timezone instead of UTC. We pin the PHP timezone to UTC on every oPodSync instance, document the AntennaPod-side workaround for users still on older client builds, and watch the upstream fix. New deployments get the correct behaviour by default.
If the second device synced before the first had finished the initial push, yes. This is upstream oPodSync issue 29. The recovery is the AntennaPod "Force sync" control after device linking. We run a nightly SQLite dump in addition to point-in-time daily backups, so a wipe is recoverable to the previous day even when force-sync doesn't restore the local state.
Yes. The first account is created during provisioning and self-registration is disabled by default. We add further accounts through the admin UI, or enable ENABLE_SELF_REGISTRATION on instances that want open signup. A team of five with two device IDs each is the lower end of normal workload. Several hundred student or member accounts share one SQLite file without trouble.
AntennaPod 2.6.1 and later on Android using either the GPodder API or the NextCloud API, gPodder 3.10.17 desktop with the secret-token workaround, Kasts 21.08 and later on KDE Plasma, PinePods 0.6.1 and later as a web client, Music Assistant via its gPodder provider, and Podliner in a terminal. Clementine 1.4.0rc1 is known not to work upstream.

02

Migration and onboarding

We can activate your app on your own custom domain/subdomain. Examples: mydomain.com, anyword.mydomain.com.
Or, on our randomized free subdomain. Example: 963.apps.danian.cloud
If you wish to use a custom domain/subdomain, select that option when ordering your app (or notify us later). We will send you the required DNS records and if needed, our tech team will modify them for you.
21 datacenter locations across six continents. You choose the region at provisioning. Application data sits in the region you choose; pick whichever is closest to your users or matches your data-residency preference.
Yes. Request a region migration from the dashboard and we run the move in the background. The system emails you when the migration completes; total transfer time depends on data volume but typical instances finish in a few hours. There is no extra charge for a region change.
Yes. Full data export is available at any time, in a portable format you can bring to any infrastructure.

03

Billing, support, and platform

€9 covers everything we do for that app: hardware in the region you choose, daily off-site backups with one-click restore, automatic security patches and version upgrades, 24/7 monitoring, SSL and firewall, and engineering support on Email/LiveChat. There are no setup fees or hidden line items. For more info see our Pricing page.
If you decide to continue, we charge €9/app/month from day 8. If you don't, the trial ends and you can export your data. No card is required for the trial, and we never auto-charge you without explicit consent.
No. The €9/month is flat regardless of how many users log into your app. Add 5 users or 50; the price doesn't change.
24/7 Live chat and email support, both staffed by engineers who run the systems. We handle DNS configuration, SMTP setup, app integrations, performance tuning, troubleshooting, and migration help. Response time is typically under an hour. There is no tier system — every customer gets the same support.
Yes. Cancel from the dashboard. We don't charge a cancellation fee, we don't lock data, and we will export your data to you on request before deletion. data to you on request before deletion.
Every customer instance is backed up daily to a separate region from the primary. We test restores. You can request a restore at any backup point within the retention window — usually 7 days for daily backups.
Your application data sits in the region you choose at provisioning — 21 datacenter locations across six continents. Account-level data (billing, account email, support ticket history) is processed centrally. Application data region is picked by you, per app.
99.9% uptime SLA on every app, every tenant. Service credits are documented at danian.co/service-level-agreement. The status page is located at status.danian.co.
When your tenant approaches the resource ceiling — the base tier holds 1 vCPU/RAM, 30 GB storage — we notify you. Resource upgrades happen with your explicit consent; we will not upgrade your tenant or charge you without it.
We wait. We don't suspend the app or delete your data on the first failed charge. We email you, you fix the card on file, and we continue.
Invoices can be downloaded from the billing dashboard in PDF the day each charge succeeds. EU VAT is added where applicable and the VAT-reverse-charge regime applies for VAT-registered businesses with a valid number.
150+ open-source apps across automation, team chat, file sync, analytics, AI, password management, email marketing, dev tools, project management, smart home, CMS, and federated social. See the full catalog →
Yes. Every instance comes with a web-based terminal and a file manager in your DANIAN management dashboard. Useful for managing your data and customizations.
Resources scale with your usage. If your app needs more vCPU, RAM, or storage, we add it — and we ask first before any change to your plan. €9 is the floor; resource-heavy workloads may price higher, but you'll always know in advance.
Yes. We have both a Partner program and an Affiliate program available. Anybody can sign up.
No contract. No minimum commitment. Cancel anytime from the dashboard with one click. The 7-day free trial requires no credit card. After the trial converts to paid, you can still cancel at any month without notice or penalty.

DEPLOY IN YOUR REGION

21 datacenter locations on six continents

Pick the region closest to your users.

United States, Germany, Finland, Singapore, Australia, Brazil, Canada, Netherlands, UK, Spain, Italy, France, Sweden, Malaysia, India, Japan, Mexico, Poland, South Korea, Chile, South Africa and more coming soon

Global Reach Map

Try managed oPodSync for 7 days

No card. Cancel from the dashboard.