Thanks for the welcome on launch day! Appreciate the warm reception an insightful questions. A few clarifications on the most common asks + some onboarding updates:
Pricing: https://scritty.dev/#pricing - self serve individual and team pilot licenses are now live!
Personal Pilot (direct): https://buy.stripe.com/00weV56jD...
Team Pilot (direct): https://buy.stripe.com/4gM00b4bv...
Enterprise (k8s/managed deployments) isn't self serve as it needs a bit of setup on our side, so please reach out directly and we'll get you going
Personal + Team, you're up and running in under 5 minutes on the embedded backend -- install the binary, drop in your license key, and go.
You can also hook up your own backend (qdrant/pgvector/chroma/weaviate), and our team is happy to help with that or point you at the docs.
Enterprise is our hybrid and fully air gapped options; this has variable setup time, driven mostly by your security posture, networking, and existing infrastructure. Assuming right internal resources are engaged with our onboarding team, it's typically stood up and validated within one work day.
love that it keeps everything local and still makes the corpus searchable across tools, the MCP piece is a really thoughtful bridge between agents and your own history.
scritty
@tugaytakmaz appreciate it! local capture is only a third of it, MCP is what lets agents actually read their own history back instead of it just being a glorified log. glad it clicked. (other third is the prompt.toml layer)
Hello, this solves a problem I run into quite often. I keep repeating the same project context every time I change AI tools. Having one shared memory across them all feels like a much cleaner workflow
scritty
@mathew_chang exactly. repeating “let me restate the whole project to the next tool” loop was the thing I wanted (maybe even obsessively needed) to kill. shared memory across tools feels much closer to how people/teams actually work than keeping each agent in its own silo.
finally a way to stop losing track of what claude said in that one terminal session two days ago. the local index idea is solid
scritty
@esiladindoruk haha yes exact “finally” sentiment is what I was going for. answers stay local, searchable, and not trapped inside whichever tool happened to say it. "stop losing track of what claude said in that one terminal session two days ago" swap out claude for any N agent and this is pretty much the tagline :)
Losing the thread every time you switch between assistants is quietly maddening, so keeping all of that in one place you actually own is the kind of thing I did not know I wanted until now.
scritty
@xavier_macia Our devs got tired of feeling like parrots, thank you for the validating words!