

Pacific Northwest (Seattle)


Pacific Northwest (Seattle)


I appreciate the feedback.


No this is a fair question. I think I’ll add this to our sites about page.
I’ll also paste a couple paragraphs disclaimers I added to another reddit r/selfhosted post just to save my thumbs while typing this from my iPhone. Please feel free to ask any follow on questions though.
I am a senior software engineer with over a decade of experience and a similar amount of firsthand self-hosting experience. I built this project on top of a project boilerplate I made almost entirely by hand. I have used copilot to speed up development of this application on top of the boilerplate I made. So everything is built the way I want it, on top of my own architecture, technology, and design decisions. Check out my GitHub here if you’re interested. https://github.com/gianlazz/
The features and quality improvements have been made with considerable time, engineering, and intention. While ShoshannaTM, Leolazz, and I are using copilot to accelerate development, substantial upfront deliberate design was done on our part before any feature development. Additionally, nothing is taken without thorough iteration and human review. We are professional software engineers. This project is not vibe coded. It is engineered and we take much pride in our craft and the quality of our work.


That’s a really good suggestion, thank you for your support 🙏


At this point we don’t have a concrete plan, but for the sustainability of the project I would like to monetize it eventually.
As of now we do have a ko-fi donation page set up and linked in the repo though.
What I do know for sure though is that it’s important to me that the selfhosted deployments always be maintained as full featured as possible. I’m a selfhoster myself and have been doing so for many years. I’ve thought a lot about this subject and really don’t want to f it up.
I really like the Bitwarden, Immich, or ghost blog model. “Want to use our convenient cloud hosted instance? Toss us a few bucks a year to support development. Otherwise selfhost it and you’ll still get the same full experience… it just might take a bit of work.”
I’m entertaining some kind of paid plan for professional stylists on the public cloud instance.
The selfhosters will always be our core audience though. It takes actual effort to selfhost and invest in open source, so those who do so will remain first and foremost. And ideally this good will may result in positive recommendations for our cloud offerings down the road to those less inclined to self host.


Ahh, I hadn’t tested that, that’s good to hear! Thank you for sharing.


Awesome, please feel welcome to reach out either here or on the repo if you run into any issues or questions! 🖤


Thank you, tbh I started it as just a kinda silly side project for myself and I’ve been really pleasantly surprised by it’s reception 🖤


Glad to hear you like it! We worked really hard on it and hope you enjoy it :)


Certainly, we hope you find it useful!


We hope your wife finds it useful! Please feel welcome to share any feedback either here or on the repo 🖤
You’re very welcome. Please let us know how you like it!