⠀⠀⠀⠀⢀⠠⠤⠀⢀⣿⡀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
⠀⠀⠐⠀⠐⠀⠀⢀⣾⣿⡇⠀⠀⠀⠀⠀⢀⣼⡇⠀⠀⠀⠀ verso by @parazeeknova
⠀⠀⠀⠀⠀⠀⠀⣸⣿⣿⣿⠀⠀⠀⠀⣴⣿⣿⠇⠀⠀⠀⠀
⠀⠀⠀⠀⠀⠀⢠⣿⣿⣿⣇⠀⠀⢀⣾⣿⣿⣿⠀⠀⠀⠀⠀ a personal portfolio and knowledge base,
⠀⠀⠀⠀⠀⣴⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⣿⡟⠀⠀⠐⠀⡀ two sides of the same surface.
⠀⠀⠀⠀⢰⡿⠉⠀⡜⣿⣿⣿⡿⠿⢿⣿⣿⡃⠀⠀⠂⠄⠀ your work on one, your words on the other.
⠀⠀⠒⠒⠸⣿⣄⡘⣃⣿⣿⡟⢰⠃⠀⢹⣿⡇⠀⠀⠀⠀⠀
⠀⠀⠚⠉⠀⠊⠻⣿⣿⣿⣿⣿⣮⣤⣤⣿⡟⠁⠘⠠⠁⠀⠀
⠀⠀⠀⠀⠀⠠⠀⠀⠈⠙⠛⠛⠛⠛⠛⠁⠀⠒⠤⠀⠀⠀⠀ - selfhosted, open source, and free to use.
⠨⠠⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠑⠀⠀⠀⠀⠀⠀
⠁⠃⠉⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀⠀
so. you're reading a readme. which means you're probably a developer, or deeply lost. either way, welcome.
verso is my personal portfolio and knowledge base two panels, two purposes, one app that doesn't apologize for being both. the left side is where i exist as a person: my projects, my work, my contribution graph that i pretend isn't a source of anxiety. the right side is where i think out loud: notes, docs, blog posts, half-baked ideas that maybe shouldn't be public but are anyway.
it's a wiki glued to a developer portfolio. i built it because i couldn't find anything that did both without making me feel like i was filling out a form.
here's the honest answer: i was tired.
tired of maintaining a portfolio site that was always three projects behind. tired of keeping notes in five different places. tired of notion being a whole subscription, confluence being enterprise-shaped trauma, and obsidian vaults that only i could ever see. i wanted one place - mine, self-hosted, permanent - where i could put both the what i built and the why i built it.
so i built verso. because apparently the solution to "too many tools" is "build another tool." the hubris is not lost on me.
- portfolio panel — your profile, your projects, your work history, your activity. the whole "here's who i am professionally" side of things, laid out clean.
- knowledge base panel — a full wiki. write in markdown, organize into folders, link between pages, publish what you want. your public docs live here.
- real-time collaborative editor — because even personal projects deserve proper tooling.
- spaces & folders — organize your writing the way your brain actually works, not the way some vc-funded startup thinks you should.
- self-hosted, fully — your data, your server, your rules. no phone home, no "we updated our privacy policy" emails.
- open source — fork it, break it, make it yours. i won't stop you. i'll probably star your fork.
i have no idea. that's the honest answer and also the exciting one.
right now verso is personal infrastructure built for me, open-sourced because hoarding code is a bad personality trait. but i can see it becoming a few things:
it could become the go-to self-hosted alternative for developers who want a portfolio that thinks — where your writing and your projects are aware of each other, cross-linked, living in the same place. imagine a project page that automatically surfaces the blog posts you wrote while building it.
it could get an API layer. rss feeds for your public notes. embeds. a CLI for pushing markdown straight from your editor. probably an obsidian plugin that someone else builds and i take zero credit for.
it could grow a proper multi-user mode — teams, permissions, shared spaces. a studio wiki and a portfolio rolled into one, for small builders who don't want to pay for confluence and also have taste.
or it stays exactly what it is — a quiet, self-contained corner of the internet where i document things. that's also fine. not everything needs to scale.
if you use this, break something, or have an opinion - open an issue. if you build something on top of it, tell me. if you think the name is pretentious, you're right, i know, i like it anyway.
verso is a living thing. it'll change as i change. that's the point.
good luck out there.
— harsh / @parazeeknova