About Seylo
Last updated 7 August 2026
Why it exists
Most good work made with AI is lost in the place it was made. A script you spent an evening on, the prompt that finally produced the right image, the reason you chose one direction over another: all of it sits somewhere in a conversation you will never scroll back through.
Seylo exists because that work deserves to be kept as work, not as chat history. You save it into a project, as a script or a prompt or a decision, and Seylo records how one thing led to another: which script produced which prompts, which prompt produced which visual. Months later that chain is still there.
What it actually does today
Projects hold typed assets. Four views show the same work as a document list, a gallery, a status board, or a map of what came from what. Editing keeps a version history, so nothing is overwritten for good. Files can be attached. Search runs across everything you have saved.
Claude can be connected directly, which is the part that makes Seylo different from a folder of notes: it can read what you saved, write new work back into the right project, and read the decisions and references the project already holds before it writes a word.
Where it stands
Seylo is early, and built by one person. It is free to use right now, and the paid plans described on the pricing page are not yet available for purchase. Anything on the site marked Soon genuinely does not exist yet. We would rather say that than imply otherwise.
That also means the product will change, and that a message about something broken or missing reaches the person who can fix it.
Who makes it
Seylo is made by Jakub Radziejewski, alone. I’m 21, and I build things I need.
Seylo started as my own problem. I was generating scripts, prompts and images across ChatGPT and Claude, and the ones worth keeping kept disappearing into conversations I could never find again. A folder loses the context. A note loses the file. A chat loses all of it the moment it scrolls.
I also built Overthinkr, an app for people who take a thing apart in their head before doing it. I built it because I am one, which is probably also why Seylo cares so much about being able to tell which version you actually decided on.
Contact
For anything about using Seylo (a problem, a question, a feature you need), write to support@seylo.co. Replies come from a person, usually within a couple of days.
Payments, invoices and refunds go to billing@seylo.co. Integrations, resellers and anything commercial go to partners@seylo.co.
Service provider details, as required for online services in the EU:Jakub Radziejewski, Rytro 163, 33-343 Rytro, Poland, support@seylo.co.
See also the Terms of Service and Privacy Policy.