Pinkary

Self-hosted link pages and community Q&A, honestly reviewed. No marketing fluff, just what you get when you run it yourself.

TL;DR

• What it is: Open-source (AGPL-3.0) Linktree-style link page builder with a built-in social layer — feed, Q&A, follows, likes — aimed at developers and creators who want one URL for everything [README].
• Who it’s for: Developers (especially in the Laravel/PHP community), creators, and founders who want a self-hostable profile page without paying Linktree — and who like the idea of a Twitter-lite community baked in [about page].
• Cost savings: Linktree Pro runs $5/mo, Premium $9/mo, Max $24/mo. Pinkary’s hosted version at pinkary.com appears free. Self-hosted runs on a $5–10/mo VPS with full AGPL source [README].
• Key strength: Thoughtfully built with Laravel 11, 100% test coverage, SQLite-only architecture (no Redis, no separate database server), and deployed to production in 15 hours with 1,000 users in 24 [README]. That’s a signal about code quality, not just speed.
• Key weakness: The AGPL-3.0 license limits commercial reuse. The hosted pinkary.com platform is visibly struggling with bot and spam accounts. And it’s a niche community tool, not a general-purpose link page for non-technical users [website scrape][1].

---

What is Pinkary

Pinkary is two things in one: a link aggregation page (your “one link” for all your social profiles, projects, and things you want to share) and a lightweight social network where you can follow people, ask anonymous or attributed questions, and browse a community feed.

The GitHub description is honest about the positioning: “Create a landing page for all your links and connect with like-minded people without the noise.” [README]. The “without the noise” framing is doing a lot of work — Pinkary is explicitly built for a quieter, more intentional community than Twitter or Mastodon. In practice, that community skews hard toward Laravel and PHP developers, given that the project is built in Laravel 11 and was created by the same ecosystem.

The project launched fast — 15 hours from composer create-project to production, 1,000 users in 24 hours after going live [README]. That kind of traction suggests a genuinely unmet need in the developer community for a self-hostable Linktree alternative with a social angle. The team then open-sourced it, which is when the broader self-hosted community noticed [1].

As of this review, it sits at 1,521 GitHub stars under AGPL-3.0 [merged profile].

---

Why People Choose It

The third-party review landscape for Pinkary is thin — it’s a niche tool and hasn’t attracted the kind of comparison content that workflow automation tools get. What exists tells a consistent story.

When Pinkary went open-source, selfh.st’s weekly newsletter covered it alongside a headline from It’s FOSS News: “This Strange Twitter-like Platform With Social Links is Now Open-Source!” [1]. The “strange” framing is apt — Pinkary doesn’t fit cleanly into either the link-page category or the social network category, which makes it harder to explain and easier to underestimate.

Real-world usage confirms the appeal. Curt Sheller, who runs LearningUkulele.com (a music education site with 20+ years of content), uses Pinkary as his link hub, featuring it prominently on his about page as a way to surface his most important links in one place [2]. That’s a non-developer using the tool exactly as intended — proof the pitch lands outside the PHP bubble.

The reasons people pick Pinkary over Linktree or Bento are predictable once you hear them:

License and ownership. Linktree, Bento, and most link-page tools are pure SaaS — you don’t own your data, you can’t move it, and the vendor controls what features exist. Pinkary’s source code is yours to run. AGPL-3.0 means modifications must stay open-source, but for self-hosting personal or team tools, that restriction doesn’t bite.

The social layer. Linktree is static — a list of links, full stop. Pinkary includes a community feed, follows, Q&A (anonymous questions with public answers), and discovery features. For founders and developers who want one URL that also lets people connect with them, that’s a meaningful difference [about page].

Cost. The hosted pinkary.com is free. Self-hosting on a $6 VPS is effectively free after setup. Linktree Pro is $60/year, Premium is $108/year, Max is $288/year. For a personal tool with no meaningful per-user operating costs, those numbers are hard to justify when the open-source alternative exists [README].

Code quality for a tool built fast. The README is upfront that the initial code shows signs of the 15-hour sprint, but the team followed it up with 100% test coverage via Pest, PHPStan static analysis, Laravel Pint for code style, and Rector for PHP version upgrades [README]. That’s not typical for a weekend-launch side project. It signals a maintainable codebase, not throwaway code.

---

Features

Based on the README and the about page:

Link page:

• Create a profile with username and bio [about page]
• Add links to social profiles, work, projects — anything you want to surface [about page]
• Single shareable URL as your “one link” [website]

Social layer:

• Chronological feed of people you follow [about page]
• Trending feed for discovery [website]
• Follow / unfollow users [about page]
• Anonymous and attributed Q&A — ask someone a question, they answer publicly [about page]
• Likes on posts and questions [README]
• User discovery browse [about page]
• Notification system [website scrape]

Technical stack (relevant for self-hosters):

• Laravel 11 with Livewire for reactive UI without a separate JS framework [README]
• SQLite for everything — database, sessions, queue, cache [README]. No Redis dependency, no PostgreSQL required.
• PHP 8.3 with GD extension [README]
• Node.js 16+ for asset building [README]
• Queued jobs via SQLite queue driver [README]
• 100% test coverage (Pest), 100% type coverage (PHPStan) [README]

What’s missing (relative to competitors):

• No analytics dashboard (Linktree Pro has click tracking)
• No scheduled posts or content calendar
• No payment integration or “link to buy” features
• No mobile app (web only)
• No embeddable widgets

---

Pricing: SaaS vs Self-Hosted Math

Pinkary (hosted, pinkary.com): Appears free. No pricing page is linked on the about or homepage. The README mentions Mailcoach for email as the only paid external service, and DigitalOcean with Laravel Forge for hosting [README]. Whether the hosted service will eventually add paid tiers is unknown.

Self-hosted (community edition): $0 software cost under AGPL-3.0. Infrastructure is the only cost.

What you need to self-host:

• A Linux VPS: $5–10/mo (Hetzner, DigitalOcean, Contabo)
• PHP 8.3 with SQLite, GD, and standard extensions
• Node.js 16+ for building assets
• A domain and reverse proxy (Nginx or Caddy) for HTTPS
• An SMTP provider if you want email delivery (not Mailcoach — that’s what the pinkary.com team uses; you’d use Mailgun, Postmark, or similar)

No Redis. No PostgreSQL. SQLite handles all of it. This is a genuine simplicity win for self-hosters — one fewer moving part to configure, maintain, or break.

Linktree for comparison:

• Free: unlimited links, basic customization, no analytics
• Starter: $5/mo — analytics, email list integration
• Pro: $9/mo — priority support, more customization, scheduling
• Max: $24/mo — payments, lead capture, advanced analytics

For a solo developer or founder who just needs a link page and doesn’t need Linktree’s analytics or payment features, self-hosting Pinkary on a $6 VPS saves $60–$288/year versus Linktree. More importantly, you own the instance, the data, and the Q&A community you’ve built on it.

---

Deployment Reality Check

The README’s install path is clear: clone the repo, install Composer and NPM dependencies, copy .env.example, generate an app key, create the SQLite database file, run migrations, link storage, build assets in watch mode, and start the dev server [README]. For a developer familiar with Laravel, this is routine — roughly 20–30 minutes.

The production setup the Pinkary team uses is DigitalOcean with Laravel Forge managing the server, running Ubuntu 22.04 on a 2 vCPU / 2GB / 25GB Disk droplet [README]. That’s a $12–18/mo Droplet depending on region. Laravel Forge adds $19/mo. If you know Forge, that’s the easiest path. If you don’t, you can configure Nginx and Supervisor yourself — the only services you’re running are PHP-FPM and a queue worker.

What can go sideways:

The SQLite-everything architecture is simple to set up but has scaling limits. A personal link page with a community feed handling hundreds of concurrent users will eventually hit SQLite’s write concurrency ceiling. The Pinkary team’s own production server is a 2GB Droplet — that’s their scale baseline. For a personal or small-team deployment, it’s fine. For a multi-tenant platform or a community expecting thousands of daily active users, you’d want to evaluate switching to PostgreSQL (which Laravel supports with a config change).

Email delivery requires a separate SMTP provider. The README notes the dev environment logs emails instead of sending them, and suggests Mailtrap for local testing [README]. In production you’ll need Mailgun, Postmark, SES, or similar — budget $0–10/mo depending on volume.

The bot/spam problem on hosted pinkary.com. The website scrape of the live feed shows the community is not healthy. One user wrote: “Pinkary was a cool idea and it is sad to see it overrun by bot and spam” [website scrape]. Multiple recent feed posts are clearly spam — healthcare market reports, cleaning service ads — sitting alongside legitimate developer content. This is a signal about the hosted platform, not the self-hosted installation, but it raises a question about whether the community features deliver value in their current state. Your self-hosted instance wouldn’t have these users, but you also wouldn’t have any community at all.

Realistic setup time: 30–60 minutes for a developer comfortable with Laravel and Linux. 2–4 hours for someone following a guide. Non-technical founders should not attempt this without help or a deployment service.

---

Pros and Cons

Pros

• SQLite-only architecture. No Redis, no PostgreSQL — just PHP and a file. This is the simplest possible self-hosting story for a web application with queues and caching [README].
• 100% test coverage and static analysis. Pest type coverage at 100%, PHPStan, Pint, Rector — this is a serious codebase, not a weekend hack [README].
• Free hosted version. pinkary.com appears free with no paid tiers, which is rare in the link-page category.
• Social layer included. Anonymous Q&A, feeds, follows — features Linktree charges for or doesn’t offer at all [about page].
• AGPL-3.0 open source. Self-host it, fork it, modify it — your data stays yours.
• Laravel ecosystem. If you already run Laravel apps, Pinkary slots into your existing mental model and toolchain [README].
• Launched fast, maintained well. 15 hours to production shows product judgment; the post-launch quality investment (100% test coverage, static analysis) shows discipline [README].

Cons

• AGPL-3.0, not MIT. You can self-host and modify it, but if you build a SaaS on top of Pinkary, you must release your modifications under AGPL. This is a real restriction for anyone thinking about commercializing it.
• The community is broken on pinkary.com. Spam and bots have overrun the hosted feed [website scrape]. If the social features were a reason you wanted Pinkary, the existing community isn’t delivering that today.
• No analytics. Linktree’s paid plans give you click-through data and UTM tracking. Pinkary has none — you’d need to add Plausible or Umami separately if you care about link performance.
• No mobile app. Web-only. Linktree, Bento, and Bio.link all have mobile apps for managing your profile.
• Niche community. The existing user base on pinkary.com skews heavily toward Laravel developers. If you’re not in that world, the “discover like-minded people” promise lands differently.
• Unknown hosting costs if you use pinkary.com. The free tier has no documented limits and no pricing page — which means you don’t know what happens if a paid tier appears.
• No multi-tenancy or team features. One instance, one user (or a small friend group). No organizational accounts.
• Requires PHP 8.3 hosting. Not all cheap VPS providers make this trivial out of the box. You’ll need to configure a PPA or compile PHP, which adds setup steps.

---

Who Should Use This / Who Shouldn’t

Use Pinkary if:

• You’re a developer (especially in the Laravel/PHP world) who wants a self-hosted Linktree alternative with a social angle.
• You want to own your link page data and not depend on a third-party SaaS that can change pricing or terms.
• You’re already comfortable deploying Laravel applications and want the simplest possible self-hosting stack (SQLite-only).
• The hosted pinkary.com is an option and you want a free link page without paid tiers.

Skip it (use Linktree or Bio.link) if:

• You’re non-technical and have no one to help with deployment.
• You need click analytics and UTM tracking built in.
• You want a mobile app for managing your profile.
• You need payment integration or “link to product” e-commerce features.

Skip it (use Bento or Carrd) if:

• You want a visually customizable landing page with design control — Pinkary’s design is fixed and minimal.
• You need embeddable widgets or integrations with marketing tools.

Skip it entirely for a SaaS product if:

• The AGPL-3.0 license is a problem for your business model — any SaaS built on Pinkary must open-source its modifications.

---

Alternatives Worth Considering

• Linktree — the incumbent. Easiest onboarding, mobile app, analytics, payment links. Paid tiers from $5–24/mo. Fully proprietary SaaS. No self-hosting option.
• Bio.link — free link page, ad-supported on free tier, cleaner than Linktree’s free tier. No social features. No self-hosting.
• Bento — developer-focused link page, free tier, good design options. Proprietary hosted-only.
• Carrd — more of a landing page builder than a link page tool. Free tier, Pro at $9–19/year. No social features. No self-hosting.
• LinkStack — AGPL-3.0 self-hosted Linktree alternative, more focused purely on the link page without the social network. Simpler deployment, but also less interesting. More user base documentation available.
• n8n + a static page — overkill, but some developers build their own link pages with a static site generator. Full control, no community features.

For non-technical founders, the honest shortlist is Linktree Free vs pinkary.com — both are free, pinkary.com just adds Q&A features in exchange for a smaller audience. For technical founders who want self-hosting, Pinkary vs LinkStack is the real comparison, with Pinkary winning on feature set and code quality, LinkStack winning on community documentation.

---

Bottom Line

Pinkary is a well-built tool that does something genuinely interesting — it tries to make your link page a place people can actually engage with you, not just click through. The SQLite-everything architecture is smart for the use case, the test coverage is unusually thorough for this kind of tool, and the fact that it went from idea to 1,000 users in a weekend says something real about the founder’s execution.

The friction points are honest: the live community at pinkary.com is struggling with spam, the AGPL license limits commercial use, and the target audience is narrow (read: Laravel developers who already know about Pinkary are disproportionately likely to be the people reading its README). For a non-technical founder looking for “Linktree but self-hosted,” Pinkary is a viable answer if someone handles the deployment for them. For a developer who wants a clean, simple, dependency-light web app to self-host and own their link page, it’s close to the best option in its category.

If the deployment is the blocker, that’s exactly the kind of one-time setup that upready.dev handles for clients.

---

Sources

1. Ethan Sholly, selfh.st — “This Week in Self-Hosted (6 September 2024)”. https://selfh.st/weekly/2024-09-06/
2. Curt Sheller, LearningUkulele.com — “All About LearningUkulele.com” (Pinkary profile usage example). https://learningukulele.com/about

Primary sources:

• GitHub repository and README: https://github.com/pinkary-project/pinkary.com (1,521 stars, AGPL-3.0 license)
• Official website: https://pinkary.com
• About page: https://pinkary.com/about