Meet the Developer
The story behind the story engine.
Taran
Developer & Founder
I started building Plottik because I wanted to write a novel - a big, sprawling one with branching timelines and more characters than I could keep track of.
I tried Scrivener, Notion, pasting chapters into ChatGPT... nothing really worked as well as I wanted. Scrivener doesn’t have AI or timelines. Google Docs is just a document. And ChatGPT forgets everything after five messages.
So I built the tool I wished existed. A desktop app where the manuscript, characters, timelines, and world-building all live together - and the AI can search across all of it.
Plottik started as a side project and turned into something I think other writers might actually need. It’s built with Rust and React, runs natively on Mac and Windows, and keeps all your data local on your machine.
I’m not a published author (yet). I’m a developer who writes. But that perspective is what makes Plottik different - it’s built by someone who understands both the craft of storytelling and the engineering needed to support it properly.
What I Believe
Your data is yours
Everything lives on your machine. Your manuscripts are never sent to our servers. AI queries go directly to your chosen provider - we never see them.
AI assists, not replaces
The AI is a research assistant that’s read your whole book. It suggests, you decide. Every edit goes through a review step before it touches your manuscript.
No Monthly Subscription
Buy the app once and use it forever.
AI features work using your own API key or local models through Ollama, so you only pay for AI usage when you actually use it.
Built for complexity
Simple stories don’t need Plottik. But if you’re juggling multiple timelines, a cast of dozens, or a world with its own rules - this is the tool for that.
Got questions, feedback, or just want to say hi?