I'm a student. I use ChatGPT and Claude every day for brainstorming, for drafting, for getting unstuck. But the second that writing touched a detector like Turnitin or GPTZero, it got flagged. Didn't matter that every idea in it was mine. Didn't matter that I'd rewritten half of it by hand. One AI pass in the process and suddenly I'm guilty until proven innocent.
I watched it happen to people around me too. A classmate lost marks on a paper she'd actually written herself, just brainstormed with AI first. A friend freelancing on the side lost a client over a false flag. It felt broken. AI is just how people write now, and the tools meant to catch cheating were punishing normal work.
So I went looking for how these detectors actually decide what's AI and what's not. Turned out there's real research behind it, an IEEE paper breaking down the exact signals they score: how varied your sentence lengths are, how predictable your word choices are, that kind of thing. And most of the humanizer tools already out there weren't touching any of that. They were just swapping words for synonyms and hoping for the best.
That gap is what got me building. I wanted something that actually engaged with the real signals detectors use, instead of a shortcut. And I wanted it free, because a student shouldn't have to pay to prove their own writing is their own.
That's Swift AI Humanizer. Not a trick. An actual attempt to solve the problem properly.
Built With
- javascript
- next.js
- node.js
- openai
- tailwind
- vercel
Log in or sign up for Devpost to join the conversation.