What this is and why it exists
About Stoka
Stoka is an artifact platform: a place where AI work is captured, retrieved, and, when you choose, shared. The core unit is the artifact — a structured record of a conversation, prompt, spec, essay, codebase, or link that should still be useful after the chat window is gone.
Three principles
Solo-first
The product has to feel good before anyone else is invited. If capturing your own AI work, retrieving it later, and keeping a personal library is not already worth using alone, the rest is noise.
Sharing-not-posting
The default is private. The main move is sending an artifact to a handle, not throwing it into a feed and hoping an algorithm does something useful with it.
Trust-inverted discovery
Strong anonymity should lead to richer discovery, not worse discovery. When users can keep distance from real-name identity, they are more willing to expose the work itself, which makes search and sharing better.
Why this exists
AI has made a weird thing normal: conversations now contain real intellectual property, but most of that work still dies in chat scrollback. A prompt that finally clicked, a design rationale buried in message 48, a spec you only half-finished, a codebase investigation you will need again in two weeks. Useful work disappears because the container was never built to remember it.
Stoka exists because that is a bad trade. The artifact is the answer: capture the work, structure it hard enough that retrieval works later, and keep the default private until the author decides it should move.
Where we are
Phase 0 is live now: a public discovery terminal where the thesis, docs, writing, and reference integrations are visible.
Phase 1 is next: solo capture from pasted conversations, a personal library, retrieval, and pseudonyms that can sign work later.
Phase 2 adds selective sharing: send artifacts to handles, keep the default private, and let public discovery stay opt-in.
The fuller roadmap lives in the specs.
How we build
Built because I needed it first. That is still the quality filter. If a flow is too annoying for me to use alone, it does not get hidden behind growth copy and called done.
Self-hosted where it matters, not as cosplay. Data locality, response time, and pricing all change when the infrastructure is yours. The platform story and the infra story are attached to each other.
One editorial nervous system across the site. Stoka is not a chatbot bolted onto a landing page. It is the same voice framing artifacts, retrieval, public discovery, and the trust rules around them.
Why the integrations exist
The six apps below are not the top-level product. They are the six live reference integrations Shay controls end to end, which makes them the cleanest place to pressure-test the platform thesis before third-party apps ever onboard.
They still sell. Pricing and features still matter. But the honest hierarchy is: Stoka is the platform, and these apps are proof that the platform survives contact with real workflows in education, life ops, writing, and voice.
Get in touch
We are interested in feedback, thoughtful criticism, and integrations that fit the thesis. Reach out at [email protected].