Is Fluxer vibe-coded?
No, Fluxer isn't vibe-coded. A person who understands the code is responsible for every code change and checks it before it ships, and anyone can look through the source code and its history on GitHub. Andrej Karpathy coined the term vibe coding in February 2025 and described it as a way to "forget that the code even exists." It means letting an AI tool write software and shipping it without reading or understanding the code.
Who builds Fluxer?
Fluxer is made by Fluxer Platform AB, a small Swedish company. Hampus Kraft, the creator of Fluxer, leads its development and has worked on it full-time since September 2025. He builds the backend, the web app and the desktop app. A second product engineer works on the iOS and Android apps, and a few contributors help.
Hampus is close to finishing a BSc in Computer Engineering at KTH Royal Institute of Technology, and his bachelor's thesis there was published in September 2025. He has also built and run large production systems for years.
I don't think vibe coding is cool, and I don't condone slop or unethical use of LLMs.
When was Fluxer created?
The first prototype of Fluxer was Hampus's high school project between 2020 and 2022, and fluxer.com opened to everyone in January 2026.
Does Fluxer train AI on my messages?
No. We never use your content to train, fine-tune or evaluate AI or machine learning models, as our terms say. Section 5 of our privacy policy lists the automated safety checks we run on it, and none of them use generative AI or LLMs.
Why are Fluxer's line counts so big?
Most of the lines that change in Fluxer's repository are translations.
From August 22 to September 28, 2026, git counted 1.10 million lines added and about 980,000 deleted, a net gain of about 121,000. Translation files were 53.5% of the changed lines, tests were 12.3%, application code was 22.8% and other files, such as config, docs and lock files, made up the remaining 11.4%.
Fluxer is available in 34 languages and regional variants, and each sentence in the app takes about five lines in each language's translation file.
One new sentence adds about 170 lines, and rewording one can make git count all 170 as deleted and added again. The app's 8,000 or so sentences come to more than 1.3 million lines of translations. New sentences start as machine-translated drafts, and people review and improve them on Fluxer's translation site.
Some of the biggest commits have months of work in them. When something more urgent came first, we had to bring the waiting changes up to date before we could ship them, and they went out in big batches once things had calmed down.
Fluxer's public history starts with one commit of nearly 1.5 million lines, dated January 1, 2026. About 800,000 of those lines are translations, and the rest is years of work from before the code was public. Starting the public history with a single commit is common practice when private code is open sourced, because a private history can contain passwords, keys and other details that shouldn't be published.
What Hampus doesn't condone
- Shipping code that nobody has read or understood. That's vibe coding.
- Flooding open source projects and communities with slop. Our anti-slop policy doesn't allow AI-made contributions from people outside the Fluxer team.
- Training AI on people's messages, files or personal data without their consent, or selling that data to AI companies. Fluxer never trains AI on your content at all, with or without consent, and section 3.1 of our terms of service also says Fluxer never sells or licenses your content for anyone else's independent use. Section 4 of our privacy policy says Fluxer never sells or licenses your personal data to anyone.
- Making sexual images of real people without their consent. Section 1 of our community guidelines bans sharing intimate material of anyone without their consent, including realistic synthetic images made with AI.
- Making any sexual image of a child. Our guidelines ban it in every form, AI-generated or not, and we report confirmed child sexual abuse material to NCMEC.
- Impersonating people or faking evidence. The guidelines ban using AI-generated media to deceive or impersonate anyone, or to pass it off as real evidence.
- Spam, fake accounts and fake engagement. Section 6 bans spam, accounts that are fake or deceptive and numbers that are artificially inflated.
Section 7 still allows AI-generated media for creative, fictional, educational and satirical use when it follows the rest of the community guidelines. Allowed doesn't mean tasteful, and individual communities can set stricter rules of their own.
Our anti-slop policy
People outside the Fluxer team can suggest changes to Fluxer's main repository on GitHub. Our anti-slop policy lets them use an LLM privately to research and plan their work. They can't submit code, text, images, audio or video made by an LLM or other generative AI, even after editing, and everything they submit must be their own work. The one exception is a disclosed machine translation of their own writing.
How many lines did this page add?
This page is in 34 languages and regional variants. The English version is 64 lines long. Its 32 translations, plus its title, summary and menu link in every language, added 2,852 lines to git, about 45 times the length of the English page. Each translation started as a machine-translated draft, the same way the app's sentences do.