Skip to main content

Fully Managed Pixelfed
as a Service

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

Pixelfed is the open-source ActivityPub-native photo platform — albums, stories, comments, hashtags — combining the public-square reach of Instagram-style sharing with the privacy and control of self-hosted infrastructure. Your posts federate to Mastodon, Threads, Misskey, and the wider fediverse without anyone signing up for anything.

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

Pixelfed

Pixelfed

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 →
Pixelfed Preview Image

ABOUT THE SOFTWARE

What is Pixelfed

Pixelfed is open-source software for running your own photo-sharing platform. It looks and feels like Instagram — albums, stories, comments, hashtags — but it federates across the open social web, has no ads or algorithmic feed, and lives at a domain you control. License: AGPL-3.0.

The project was started in 2018 by Daniel Supernault and is now developed by a small team supported by Patreon, Open Collective, and NLnet/NGI0 grants. A successful January 2025 Kickstarter funded the in-progress formation of the Pixelfed Foundation as a not-for-profit. Built on Laravel with PHP, Redis-backed Horizon queues, and compatible storage.

Pixelfed runs across the fediverse: roughly 300,000 to 500,000 accounts across a few hundred public instances as of early 2025, with the flagship pixelfed.social briefly the second-largest single instance in the fediverse after the official iOS and Android apps shipped in January 2025. Notable instances include pixelfed.social, pixelfed.de, pixelfed.cafe, metapixl.com, and pixey.org. The protocol stack — ActivityPub plus WebFinger plus HTTP Signatures — means a post on your instance reaches Mastodon and Threads users without anyone signing up for anything.

FEATURES

What Pixelfed does

Pixelfed is a full photo-sharing platform, not a federation shim. Albums, Stories, Comments, Hashtags, Discover, Profiles, DMs, Lists, Collections, Account Migration — the features a photo-first audience expects, with ActivityPub on top so the network effect doesn't end at your domain.

Albums up to 10 images

Multi-photo posts mirror Instagram's carousel format. Each image gets its own caption, alt-text, and CC license tag if you want.

ActivityPub federation

Posts reach Mastodon, Threads, Misskey, and other Pixelfed instances natively. Follows, boosts, replies, and DMs cross instance boundaries.

Account Migration

Move your identity and followers from one Pixelfed instance to another (or to a compatible ActivityPub server) using the Move activity.

Instagram archive import

Drop in the JSON export from Instagram's Accounts Center and Pixelfed reconstructs your post history on your domain.

Stories with fan-out

Ephemeral 24-hour posts. v0.12.6 rewrote the StoryIndexService for performance on instances with many remote followers.

Official iOS and Android apps

Launched January 2025. Mastodon-API-compatible, OAuth-driven, sign in with any Pixelfed instance handle.

AVIF, HEIC, WebP, libvips

Modern image formats supported natively as of v0.12.6. ICC color profiles are preserved through resize and transcode.

Admin tooling

Moderated Profiles, Authorize Interaction, Domain Blocks API (Mastodon-compatible), Report queue, Legal Notice page.

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 Pixelfed

In January 2025, Pixelfed shipped official iOS and Android apps the same week Facebook began deleting links to pixelfed.social. The convergence pushed photographers, collectives, and small media outlets to start their own instances rather than depend on Meta. Running Pixelfed is then the question of who keeps the queues moving.

Running Pixelfed in production isn't writing the install script. It's the patching cadence, the Redis Horizon worker pools, the FFmpeg pipeline that has to handle a hundred different camera formats, and the federation key rotation when an HTTP signature breaks at 3am because someone on a remote instance posted a malformed activity. That's not glamorous work. It's the work that happens, every week, on every instance that actually federates.

The most common production failure mode is the silent federation freeze: InboxValidator and InboxWorker jobs accumulate as pending in Horizon, no errors logged, no failed jobs in the dashboard, and federation just stops. The admin doesn't find out for hours or days, usually when a Mastodon follower mentions that posts aren't showing up. Causes range from a misconfigured systemd unit running Horizon as the wrong Unix user, to a Redis client mismatch, to Debian's MySQL default collation drifting away from utf8mb4_unicode_ci, to an orphaned OAuth private key. Every fresh self-host install hits at least one of these. We've fixed all of them.

REVIEWS

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

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

USE CASES

Three teams who run Pixelfed on DANIAN

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

12-PERSON PHOTOGRAPHY COLLECTIVE

Replacing twelve separate Flickr Pro accounts with one collective instance at photos.collective.example

Lisbon-based documentary collective, region: Spain datacenter. Closed registration with admin-curated onboarding; OAuth enabled for the official Pixelfed iOS app; AVIF and HEIC ingest for iPhone shooters; max 10 images per post; weekly off-site backup. Adobe Lightroom export pipes into an S3 staging bucket, then up to Pixelfed via the API.

UNIVERSITY PHOTOJOURNLISM PROGRAM

60 students, three faculty, one teaching instance behind the institution's OIDC IdP

Midwestern US program, region: USA datacenter. Email-domain allowlist on .edu; OIDC SSO bound to the institutional IdP so students don't manage a second password; federation enabled with the FediThreat blocklist applied; Stories disabled; EXIF stripped on upload; quarterly account-export so graduating students keep their work.

REGIONAL TOURISM BOARD

Six staff plus 400 invited community contributors seeding place-tagged Alpine photography

Alpine region, region: Germany datacenter. Place tagging enabled (128,769-city import); EXIF GPS preserved, opposite of the journalism case; German, Italian, and French translation packs; Mastodon cross-posting to the board's existing presence; public album-carousel embeds feed the main tourism website.

COMPARISON

Four ways to run Pixelfed

The path you pick isn't really about Pixelfed. It's about who keeps the queues moving when federation breaks at 2am. The math at 1, 5, and 10 photographers is below, in real numbers, no asterisks.

 PATHMONTHLY COST 1/5/10 USERSSETUP TIMEOPS TIME PER MONTHYOUR ROLE
Flickr Pro
(proprietary SaaS)
$6.83 / $34.15 / $68.30 (annual billing)
$11 / $55 / $110 monthly billing
5 minutes0 hoursPay invoices, accept ToS changes, accept the flickr.com handle
Self-host on a $24/mo production-class VPS
$44+ infrastructure
+ €60-240/mo in sysadmin time
5-10 hours1-2 hoursPatch monthly, fix Horizon at 2am, rotate OAuth keys, debug S3 path-style addressing
Self-host on a home server
(Synology DS923+ or HP ProLiant ML30 Gen10)
€210-667/mo effective
hardware + electricity + business internet + off-site backup + ops time
1-2 weekends2-4 hoursAll of the above + thermal + UPS + escalating with your ISP when uplink drops
DANIAN Managed Pixelfed €9 / €9 / €9Same day0 hoursPost photos. We patch, monitor, back up, and stay on call.

Flickr Pro is genuinely cheap per individual user and a fair answer if all you want is a photo backup with social features. It's also someone else's platform, and the math stops working the moment your collective grows past two or three photographers each on a separate Pro account. Self-hosting on a VPS is the right call if you have a developer in-house and a tolerance for 2am pager work; Coolify on a $24 production-class VPS is a genuinely good DIY path for that buyer. Home server gives you full physical control and stops making sense the moment your business-grade internet has a four-hour outage. Managed Pixelfed gives you the one thing the other three paths don't: someone whose name shows up in a chat window when the queue stops moving.

BY INDUSTRY

Pixelfed for specific industries

Pixelfed is general-purpose, but a few industries have non-negotiable operational requirements that shape how the instance gets configured. The four below are where we see the most considered conversations — each with a specific regulation or standard, a configuration choice we make, a real workflow, and a concrete number.

For studios that license their work, copyright handling is operational, not optional. DMCA §512 takedown procedure for US-served images puts procedural obligations on the operator: a designated agent, a takedown queue, a published Legal Notice. Pixelfed v0.12.6 ships an admin Legal Notice page and a moderator Report queue out of the box.

On DANIAN, we preserve EXIF and IPTC metadata on upload so authorship signatures travel with the file, enable per-post Creative Commons license tagging, and provision a starter Legal Notice template that points at your DMCA designated agent. A typical workflow: a photographer uploads a JPEG with embedded CC-BY-NC-4.0 metadata, Pixelfed displays the license badge on the post, and remote reblog activity that crosses a CC-incompatible boundary surfaces in the federation moderation report through the Domain Blocks API.

Concrete spec: Pixelfed allows up to 10 images per post — useful for studios that used to hit Instagram's carousel cap.
Photo programs in higher-ed and K-12 operate under student-data rules. In the US, FERPA (34 CFR Part 99) governs student photo handling; outside the US, similar privacy frameworks impose comparable obligations on the institution as data controller. DANIAN does not hold student-data certifications — the institution remains the data controller and we operate as a processor whose configuration enables your posture.

The standard config: closed registration with an email-domain allowlist on the .edu address, OIDC SSO bound to the institutional IdP so students don't manage a second password, EXIF strip-on-upload, federation disabled by default until the institution decides whether to federate. A typical workflow: a photojournalism class section uses a hashtag, faculty grade via the Admin Reports dashboard, and at semester end the institution exports student data through Pixelfed's export pipeline.

Concrete spec: v0.12.5 raised the max photo size from 50MB to 1GB — wide enough for high-resolution scans common in fine-art curricula.
For reader-submitted photos of protests, public officials, or sensitive events, source-protection best practice is to strip EXIF GPS and device identifiers on the way in. The Reporters Without Borders and Freedom of the Press Foundation digital-security guides treat this as the operational minimum.

The standard config we ship: MEDIA_EXIF_DATABASE="alse, a pre-upload EXIF stripper in the queue pipeline, registration restricted to staff plus verified contributors, and Authorize Interaction enabled so remote replies route through a moderation layer. A typical workflow: a reader submits a phone photo of a city-council meeting through the iOS app, Pixelfed strips EXIF on ingest, the editor reviews via the moderated-profiles flow added in v0.12.4, and the post publishes on the outlet's domain and federates to its Mastodon followers.

Concrete spec: ActivityPub delivery defaults to 10 parallel deliveries with a 30-second timeout per remote inbox, so a single breaking-news post reaches a thousand-follower Mastodon audience in roughly five to eight minutes on a healthy queue.
For museums and archives, image fidelity is the whole point. The operational standards in this space are IIIF for image presentation and Dublin Core or VRA Core for metadata. Pixelfed isn't natively IIIF-compatible, but its public API plus S3 backend plus CC license tagging make it a viable patron-facing layer alongside an IIIF backend.

The standard config: preserve full EXIF and IPTC, enable the AVIF and libvips pipeline added in v0.12.6 so embedded ICC color profiles survive resize and transcode (a non-trivial requirement most consumer image platforms strip without telling you), expose the v1.1 public API so the main museum site can pull collections. A typical workflow: a regional museum uploads a curated rotation of 200 archival photographs per month tagged with collection metadata in the caption, ActivityPub-following users on Mastodon and other Pixelfed instances see them appear chronologically with no algorithmic reordering, and the museum's WordPress site embeds the Pixelfed feed via WordPress-ActivityPub.

Concrete spec: v0.12.6 preserves embedded ICC color profiles through resize and transcode — most consumer platforms strip them silently.

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

This is the most common Pixelfed support call we get. We run a check at provisioning that catches it: Horizon must actually be running as the same Unix user that owns the repo and the Redis socket, REDIS_CLIENT and REDIS_PATH or REDIS_HOST must agree, the OAuth private key at storage/oauth-private.key must exist, and HTTP signatures must validate against an in-sync system clock. We wire all of this in the install pipeline so the InboxValidator and InboxWorker jobs don't end up silently pending in Horizon.
Both work; MySQL and MariaDB are the well-trodden path and have had the deepest production exposure. PostgreSQL is supported via Laravel's database abstraction but has historically been a second-class path with sporadic issues at federation edges. On DANIAN we default to MySQL.
Yes, as of v0.12.6 — that release added native AVIF, HEIC, and WebP handling via libvips, with ICC color profiles preserved through resize. We turn this on by default. Older self-hosts running v0.11.x or v0.12.5 still need to convert client-side; if you're migrating in, we upgrade you to current stable before the cutover.
Yes. Stories were rewritten in v0.12.6 with a new StoryIndexService for performance on instances with many remote followers. We size the Horizon worker pool to keep story-fanout latency under a few seconds on the typical instance.
Set OAUTH_ENABLE="1" and generate Passport keys. We do both at provisioning. Authorize Interaction support added in v0.12.4 also fixes remote-interaction redirects, which used to break the "open in app" flow from Mastodon.
No. DMs exist but are not end-to-end encrypted. We don't advertise otherwise. If E2E messaging matters to your use case, treat Pixelfed DMs as the same trust model as Mastodon DMs — server-readable.
Yes. Admin Settings, max_account_size, added in v0.12.0. We expose the toggle in the DANIAN dashboard.

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.
Yes. Pixelfed accepts the JSON-format archive that Instagram exports from Accounts Center. The pipeline has had bugs historically — most recently around S3 ownership when import runs as root in Docker — fixed properly in v0.12.5.

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 Pixelfed for 7 days

No card. Cancel from the dashboard.