Loops

Open-source short-form video, honestly reviewed. No marketing fluff, just what you get when you self-host it.

TL;DR

• What it is: Open-source (AGPL-3.0) federated short-form video platform — think TikTok, but the server lives on your hardware and the algorithm answers to you, not advertisers [1][2].
• Who it’s for: Privacy-conscious creators, community organizers, and fediverse enthusiasts who want vertical video without handing their content and audience data to ByteDance or Meta [2].
• Cost model: No SaaS tier exists — it’s self-hosted only. The software is free; you pay for a VPS and object storage. Fastly CDN is available for free through their Fast Forward program [1].
• Key strength: Native ActivityPub federation — videos and interactions travel across Mastodon, Pixelfed, and other compatible fediverse servers without any additional setup [1][2].
• Key weakness: 355 GitHub stars and currently in open beta. This is genuinely early-stage software. No established independent instance network, no large creator base, and no third-party reviews exist yet to validate real-world stability [1].

---

What is Loops

Loops is a vertically-oriented, short-form video platform built on ActivityPub — the same open protocol that powers Mastodon and Pixelfed. The project describes itself simply as “the federated short video sharing platform” [1]. The homepage pitch is more aspirational: “All the fun of short-form video, none of the corporate control” [2].

What separates it from uploading a video to Mastodon or PeerTube is the product focus. Loops is built specifically around the thumb-first, vertical-swipe short video format that TikTok and Instagram Reels normalized — a chronological Following feed plus a For You feed, a creator-first in-app camera, rich threaded comments, likes and reposts that propagate across the fediverse. This isn’t a generic video hosting tool with short-video bolted on. The entire UI and content model is organized around the loop [2][3].

The project is funded through NGI Zero Core, a program established by NLnet with support from the European Commission’s Next Generation Internet initiative [1]. Infrastructure costs are subsidized by Fastly’s Fast Forward program, which provides CDN and object storage for qualifying open-source projects [1]. That matters: it means the project has real institutional backing and isn’t solely dependent on donations to survive.

It was built by the same team behind Pixelfed (the federated Instagram alternative), which gives it a credible pedigree in the ActivityPub space. Development is active — the GitHub repository shows CI/CD pipelines across JS build, ESLint, Prettier, TypeScript checking, Laravel Larastan, and PHP Pint, suggesting a reasonably mature engineering process for a project of this size [1].

One important caveat before going further: Loops is in open beta. As of this review, no established third-party reviews or independent benchmarks exist. Everything below is based on primary sources — the GitHub repository, official website, and feature documentation [1][2][3]. Take claims about production stability with appropriate skepticism.

---

Why people choose it

Without independent reviews to synthesize, the honest answer is: people choose Loops because the alternative is TikTok, Instagram Reels, or YouTube Shorts — and those platforms own your audience, sell your data, and can deplatform you without appeal.

The fediverse pitch for Loops is structurally similar to the case for Mastodon over Twitter: you control the server, you choose the moderation rules, and your content isn’t optimized for advertiser retention. For a creator who built an audience on TikTok and watched it disappear during a ban scare or an algorithm reset, the appeal of owning your infrastructure is tangible.

The ActivityPub federation angle adds a genuine multiplier effect that centralized alternatives can’t match: a video you post on a Loops instance is potentially reachable by users on Mastodon, Pixelfed, and any other compatible ActivityPub server — without requiring those users to create a Loops account. Your audience can follow you from wherever they already are in the fediverse [2].

What Loops is not is a TikTok-scale audience replacement. The creator pool today is tiny. If reach is your primary metric, Loops is the wrong tool. It’s the right tool if you’re building a contained community — a niche interest group, a local organization, a privacy-focused creative collective — where you want short-video format without corporate surveillance.

---

Features

Based on the README and official feature documentation [1][2][3]:

Feeds:

• Chronological Following feed — shows content from accounts you explicitly follow, no algorithmic reordering [2]
• For You feed — surfaces content from across Loops instances and ActivityPub servers, driven by engagement, hashtags, and social graph signals — no ad targeting [2]
• Web browser access plus official mobile app [2]

Camera and creation:

• Built-in vertical video camera with lens switching and captions [2]
• Post directly from the app without exporting to a desktop first [2]

Engagement:

• Threaded comments with replies, likes on replies, and @mentions [2]
• Likes, reposts, and shares that federate across compatible ActivityPub servers [2]
• Hashtag support for topic-based discovery [2]

Federation:

• ActivityPub protocol — interoperable with Mastodon, Pixelfed, and other fediverse apps that support video [2]
• Videos and interactions travel beyond your instance to the broader social web [2]

Notifications:

• Granular notification controls for likes, follows, mentions [2]
• Push notification support listed as coming soon [2]

Technical:

• REST API with official documentation [1][4]
• Localization via Crowdin (translation infrastructure in place) [1]
• Active CI/CD pipeline with type checking, linting, and static analysis [1]

What’s missing or unclear:

• No SSO, LDAP, or enterprise team management features (this is an individual/community creator tool, not a corporate platform)
• Push notifications explicitly listed as not yet available [2]
• No documented content moderation tooling visible in public materials — critical for any community-facing deployment
• No video transcoding details published — you’ll need to evaluate storage and processing requirements independently

---

Pricing: SaaS vs self-hosted math

This is where Loops diverges from the typical SaaS-replacement story. TikTok and YouTube Shorts are free to users. The cost of using them isn’t monetary — it’s your data, your audience portability, and your dependence on their continued goodwill. A comparison in dollar terms is misleading here.

The real calculation is different:

Self-hosted Loops:

• Software: $0 (AGPL-3.0) [1]
• VPS: $6–20/month depending on traffic and storage requirements
• Object storage for video files: variable — video is storage-intensive. A small community of 100 active creators uploading several clips per week will realistically need 50–200GB+ within months. At Backblaze B2 prices (~$0.006/GB), 100GB = ~$0.60/mo in storage costs plus egress
• CDN: potentially $0 via Fastly Fast Forward program if your project qualifies [1]
• Your time to deploy and maintain

Commercial short-video platforms (for comparison):

• TikTok for Creators: free, ad-supported, zero infrastructure cost, zero data sovereignty
• Vimeo (if you want ad-free hosting): $20–108/month depending on storage tier
• Wistia: $19–319/month
• Mux (video infrastructure): usage-based, roughly $0.0035/min of stored video + $0.0003/min delivered

For a privacy-first community or small creator group, self-hosting Loops on a $10 VPS plus $5–10 in object storage comes to $15–30/month with full control. For individuals who just want to post videos without corporate surveillance, the honest answer is that TikTok is still free and will reach more people — Loops is a values trade-off, not a cost trade-off.

For organizations — nonprofits, local groups, niche communities — that want a branded short-video presence with their own moderation rules and no algorithmic meddling, the math shifts. A $20/month self-hosted instance is meaningfully cheaper than Vimeo Business and gives you something Vimeo cannot: federation with the broader fediverse.

---

Deployment reality check

The README points to a separate INSTALLATION.md file for setup instructions and official API documentation at docs.joinloops.org [1][4]. This is the correct structure, but it means there’s no quick install summary to evaluate here.

What we know about the stack from the CI configuration [1]:

• PHP backend (Laravel, given the Larastan and Pint CI steps)
• JavaScript/TypeScript frontend
• Standard enough that it should deploy on any Linux VPS with PHP, a database, Redis, and object storage

What you should assume you need:

• A Linux VPS (4GB RAM minimum is a reasonable assumption for a video platform at any real load)
• PostgreSQL or MySQL
• Redis
• S3-compatible object storage (essential — video files cannot live on the VPS disk sustainably)
• A domain and reverse proxy (nginx or Caddy) with HTTPS
• SMTP for notifications
• Optionally: Fastly CDN if you qualify for Fast Forward

Realistic time estimate: For someone comfortable with Laravel deployments and Docker, probably 1–3 hours to a working instance. For a non-technical founder following a guide, expect a full day including storage configuration — video platforms have more moving parts than a typical web app because of the media pipeline.

The honest uncertainty: Because Loops is in open beta with no third-party production deployments publicly documented, the real operational complexity is unknown. Video processing, storage scaling, and federation edge cases tend to surface problems that don’t appear in staging environments. Budget time for troubleshooting.

---

Pros and cons

Pros

• AGPL-3.0 license. You can self-host, fork, and modify freely. AGPL requires sharing modifications, which is appropriate for a community platform — changes that improve the software come back to the community [1].
• ActivityPub federation built-in. Your instance connects to the broader fediverse immediately. Users on Mastodon and Pixelfed can follow and interact with content without joining your instance [2].
• NLnet / EU funding. Not a VC-funded startup with an exit strategy. The NGI Zero Core grant structure means the project’s incentive is to remain useful open-source infrastructure, not to be acquired or paywalled [1].
• Fastly infrastructure. Free CDN and object storage for qualifying projects is a genuine operational advantage — global video delivery without per-GB egress costs [1].
• Purpose-built for short video. This isn’t a generic CMS with video support. The product is designed around vertical swipe, creator tools, and the short-video UX pattern [2][3].
• No ads, no tracking. The product explicitly commits to no dark patterns and no ad-targeting infrastructure [2]. For privacy-sensitive communities, this matters.
• Active engineering. Multiple CI pipelines, TypeScript type checking, static analysis — the codebase shows disciplined development practices for a project of this size [1].

Cons

• 355 GitHub stars. This is a small project. In practical terms: smaller community, fewer people finding and fixing bugs, fewer deployment guides, less battle-tested. n8n has 100K+ stars; Pixelfed (the sister project) has 5.5K. Loops is significantly earlier than either [1].
• Open beta. Not production-stable by the project’s own labeling. If you’re building a community on this, you’re accepting early-adopter risk [2].
• No third-party reviews. Zero independent assessments exist as of this writing. Every claim on the website is unverified by outside users [2].
• No push notifications yet. Explicitly listed as “coming soon” — a significant gap for a mobile-first product [2].
• Content moderation tooling unknown. Any community-facing platform needs admin moderation tools. What exists for instance operators to handle spam, abuse, and federation blocks is not publicly documented.
• Video storage costs scale fast. Unlike text-based fediverse software (Mastodon), video platforms have steep storage growth curves. Budget accordingly — this is not a set-it-and-forget-it $6/month deployment.
• Small fediverse video network. The value of a federated video platform depends on federation partners. Today, compatible video peers are limited. As ActivityPub video support grows across the fediverse, this improves — but today, you’re mostly talking to other Loops instances.

---

Who should use this / who shouldn’t

Use Loops if:

• You’re running a niche community (local group, hobby collective, activist organization) that wants short-video sharing without handing member data to a corporate platform.
• You’re a privacy-focused creator who values sovereignty over reach, and your audience is either already in the fediverse or you’re building a new audience from scratch.
• You have technical capacity to deploy and maintain a Laravel application with object storage — or you’ll pay someone to do it once.
• You’re building something experimental and can tolerate beta-quality software.

Skip it (wait 12 months) if:

• You need production-grade stability with documented SLAs. Check back when the project exits beta and has community deployments with operational track records.

Skip it (use PeerTube instead) if:

• You want mature, production-tested open-source video hosting with a large instance network and years of community deployments. PeerTube has 1,500+ public instances and a stable self-hosting story [primary knowledge].

Skip it (use TikTok/YouTube Shorts) if:

• Your goal is audience growth and reach. No federated platform competes with centralized platforms on raw audience size. If reach is the metric that matters, the honest answer is to use the platform where your audience already is.

Skip it (use Pixelfed instead) if:

• Your community is centered on photos rather than short video. Pixelfed is the same team, more mature, larger instance network [primary knowledge].

---

Alternatives worth considering

• PeerTube — The established open-source video hosting platform. Supports longer-form content, has a larger self-hosting community and federated instance network. More mature and battle-tested than Loops. Not purpose-built for short vertical video format.
• Pixelfed — Photo-sharing fediverse platform from the same creators. Significantly more mature (5.5K+ GitHub stars, production instances with thousands of users). Pick this if your content is image-based.
• Mastodon with video — Mastodon supports video uploads natively. For communities that don’t need a dedicated short-video UX, this is a simpler operational choice with a much larger existing network.
• Funkwhale — If your content is audio/music rather than video, Funkwhale is a more mature fediverse option.
• TikTok / YouTube Shorts / Instagram Reels — The honest alternatives. Free, massive reach, zero setup cost. The trade-off is complete data and algorithm dependency.
• Vimeo — For professional video hosting without federation, Vimeo is polished and established. No fediverse, no self-hosting, but mature and reliable.

---

Bottom line

Loops is the right idea at an early stage. The case for a federated, AGPL-licensed short-video platform is real — especially as TikTok’s political volatility makes centralized short-video platforms feel like rented infrastructure. The ActivityPub foundation is correct, the NLnet funding gives it institutional credibility, and the Fastly CDN partnership solves a real infrastructure problem for a video platform.

But 355 stars and “open beta” are not marketing modesty — they’re accurate status reports. If you’re a community builder or privacy-focused creator with technical capacity and a tolerance for early-adopter rough edges, Loops is worth deploying and experimenting with now. If you need something running reliably for a real community today, wait a year and check back.

If the deployment complexity is the blocker, that’s the kind of infrastructure setup that upready.dev handles for clients — one-time, and you own the server.

---

Sources

1. Loops — GitHub Repository (loops-server, AGPL-3.0, 355 stars). https://github.com/joinloops/loops-server
2. Loops — Official Website (joinloops.org, open beta). https://joinloops.org
3. Loops — Features Page. https://joinloops.org/features
4. Loops — API Documentation. https://docs.joinloops.org
5. NLnet — Loops Project Page (NGI Zero Core funding). https://nlnet.nl/project/Loops