Vutuv, ActivityPub, and the attempt to free professional profiles from the Microsoft silo.
I keep my LinkedIn account like an old IPMI interface in the management VLAN: you hope you won't need it day-to-day, but when the place is on fire, you don't want to start pulling cables first. The network is grating, the algorithmic B2B circus wears you down, and platform mechanics prioritize dwell time over technical substance. Yet the profile stays active. Not out of enthusiasm, but because that's where the contacts, hiring managers, and the industry gather.
The Profile Illusion
LinkedIn offers public profile sections that can be viewed in a browser without logging in. But who decides which sections remain visible to search engines or unauthenticated visitors isn't the user—it's the platform. Control over presentation and access remains subject to the vendor's rules and tests.
Data export is not data sovereignty. Sure, you can download your personal data archive, and regulatory interfaces exist within the EU. But such an export doesn't liberate data from platform lock-in: contacts, conversation history, recommendations, and above all, professional reach cannot simply be carried over to another system. Walk away, and you start from scratch.
This breaking point is precisely where Vutuv steps in. The open-source project treats a professional profile as an open, machine-readable web document rather than a walled-off resource inside a proprietary ecosystem. Whether a technically superior profile model is enough to build a functioning professional network, however, is a completely different question.
What Vutuv Visibly Does Differently
My personal test ground was at vutuv.de/spalencsar for four weeks (the account has since been deleted).
Getting started was surprisingly painless. If you don't feel like manually typing twenty years of career history into web forms, you just feed Vutuv your LinkedIn data export. The integrated parser cleanly broke down my archive and imported it without leaving half-parsed records or mangled dates that needed fixing. That saves time and tedious manual typing.
The real difference shows up the moment you load the page.
Open the profile in a fresh browser window, and you won't hit a login wall: no modal JavaScript overlay nudging you to register, no greyed-out content. In my tests, the public profile was immediately readable without an account and fully accessible without intrusive login hurdles.
The content layout is equally utilitarian. Alongside standard stages like career milestones and qualifications, you can link the assets that actually matter to developers and sysadmins: GitHub, a self-hosted Forgejo instance, and a personal blog. Link verification relies on open standards: external links can be confirmed via rel="me"; anyone with full control over their domain can alternatively prove ownership through a DNS TXT record or a .well-known file.
Then there's how data is served. According to the README and real-world testing, profiles aren't locked silos: records can be fetched directly as Markdown, JSON, XML, or vCard without login or API tokens. Posts come with a clean RSS feed. If you need write access or want to connect private profile areas, you use the documented API with standard authentication via personal access tokens or OAuth 2. For simply reading the public profile, a plain curl does the job.
When it comes to monetization, the project relies on static text ads instead of programmatic ad networks. According to the operator guide, the ad system is disabled by default on self-hosted instances; text ads can, however, be served on the central reference instance vutuv.de. It's not a premium subscription model and not a programmatic tracking network, but it remains an ad system.
Under the Hood: Elixir, BEAM, and ActivityPub
The reason Vutuv doesn't feel like typical web bloatware lies in its architecture. The project is built on Elixir and the Phoenix Framework, running on the Erlang VM (BEAM). For admins and engineers, that's solid ground: the system benefits from high concurrency, fault tolerance, and dependable scalability under load. Initial HTML is delivered server-side; Phoenix LiveView handles interactivity without turning the whole frontend into a heavy single-page application.
The architectural lever is in the protocol. Vutuv supports the W3C standard ActivityPub, docking directly into the Fediverse. With federation enabled, a profile acts as a standalone Fediverse actor. Anyone on Mastodon or another federated server can follow a profile like @wintermeyer@vutuv.de right from their familiar client, read posts, and reply.
To follow someone professionally or see their updates, you don't need an account on the same service. The participation in the Fediverse is optional. Each member decides for themselves in their profile settings. And anyone running Vutuv as a private instance for a company or organization can completely disable external federation according to the operator guide.
ActivityPub isn't a silver bullet against platform lock-in. It merely ensures that a profile doesn't strictly have to live on the same service as its followers. Contacts, reach, and moderation rules don't magically migrate along with it. Technical interoperability is there. What Vutuv lacks today isn't another protocol, but a critical density of people actually working together, hiring, or recruiting.
The Price of Independence: Self-Hosting and Operational Reality
Vutuv is released under the MIT License and can be run on your own infrastructure. But open source doesn't mean turnkey. For production self-hosting, the operator guide documents PostgreSQL, a mandatory SMTP relay, and a recommended reverse proxy. Depending on enabled modules, additional dependencies come into play. Manageable for seasoned admins, but it claims maintenance time.
The real operational friction point is email delivery for passwordless authentication. If you don't run a properly configured SMTP relay or rely on a trustworthy delivery provider, you risk delivery failures. SPF, DKIM, DMARC, and sending reputation remain your responsibility. If the login PIN doesn't arrive, access is locked out.
On top of that comes responsibility within the federation network. Opening accounts for third parties or participating publicly in the Fediverse means managing more than database backups. Moderation, spam mitigation, instance blocklists, and legal compliance—like GDPR data requests—can quickly become daily chores.
I had initially made a pragmatic choice here: I used the central instance vutuv.de rather than hosting a dedicated instance myself. Anyone wanting full independence down to the last mile must be prepared to pay for it in routine administration time.
The Reach Dilemma
As of September 28, 2026, after three weeks of use, my counter on Vutuv sits at three contacts and two followers. That's hardly an empirical field study, but it reflects practical utility without sugarcoating: right now, my profile serves as a clean, open web business card. Career-relevant inquiries haven't materialized so far.
A profile is simply not a network yet. A viable professional network doesn't stem from a data schema, but from real market participants: hiring managers scouting candidates, developers recommending peers, and companies awarding contracts or posting jobs. These actors go where the pool is already filled. You can build the most modern datacenter in the middle of nowhere: if there's no road leading to it, nobody is driving there.
ActivityPub handles cross-service addressing, but it doesn't automatically carry career-relevant demand with it. A candidate marketplace comparable to LinkedIn Recruiter—complete with advanced search filters, InMail, and embedded talent pipelines—is simply not something I've observed there. HR departments and headhunters won't abandon established workflows and integrated ATS interfaces without compelling reason.
In the end, the obstacle isn't a lack of ideological willingness, but plain market dynamics and added overhead. Vutuv asks people to take yet another platform seriously and maintain it, whereas LinkedIn bundles candidates, discovery tools, and ingrained routines in one place. As long as the switching costs remain noticeably higher, an open profile remains primarily one thing: a technically sound business card that the actual job market simply bypasses.
Update Oct 5, 2026
Crash Landing in the Fediverse
Four weeks after initial setup, the experiment is over: the Vutuv profile is deleted. Not out of frustration with the software, but because of the sobering realization of just how far technical idealism and day-to-day professional reality are apart.
A protocol does not create a labor market.
Opening the feed on Vutuv doesn't land you in technical debates on architectures, deployment pipelines, or systems administration. Because of ActivityPub federation, it instead pulls posts from neighboring networks like Pixelfed directly into the timeline: macro shots of leaf beetles on sea thrift flowers, Sunday greetings, and casual snapshots. For a photo-sharing portal, that's completely fine. In a service pitching itself as a professional alternative to LinkedIn, it is pure noise.
Compounding this is the absence of real corporate presence.
Large enterprises and upper mid-market companies maintain at best an isolated, sporadic operational presence in the Fediverse. Whatever corporate handles surface there are almost universally unofficial bots, RSS relays, or mirrored streams from X. A viable recruiting marketplace backed by major employers and professional HR departments is nowhere to be found—especially without service level agreements, centralized compliance, and integration with existing applicant tracking systems. For enterprise HR, what matters is market penetration, legal liability safeguards, and workflow automation.
Mobile usability hits an immediate dead end as well.
There is no native app tailored for a professional context; on mobile, you are relegated to generic Mastodon clients. That degrades the purported business network into just another social media timeline where commercial networking gets buried between private feeds.
Ultimately, Vutuv illustrates the exact structural bottleneck that even XING couldn't overcome in the DACH market: you cannot breach LinkedIn's network effect with a handful of open protocols. The market is saturated, and nobody needs yet another niche alternative where the same twenty open-source enthusiasts echo-chamber each other.
As an open web business card, the project is a neat idea. But for that purpose, you don't need a third-party platform burdened with a bus factor of 1 and advertising banners on your profile: your own domain and a clean Git repository remain the only dependable anchor for your resume. And for the real B2B market, LinkedIn remains exactly what it was from day one: the unloved, but indispensable IPMI interface.