Keystone retweeted
Just redesigned the @keystone_build landing from scratch π₯³
@posthog was showing high bounce rate and low scroll depth, people weren't getting it.
β¨New focus: live MCP demo above the fold, and a visual identity that doesn't look like every other dev tool.
β keystoneapp.dev
Keystone retweeted
Currently building the first version of the Keystone MCP server, integrating it with @cursor_ai and @claudeai π
The next few days are going to be interesting, time to put it to the test with real projects πͺ
@keystone_build
First look at Keystone.
Connect your GitHub repos and start tracking every decision, trade-off and rationale automatically π
βοΈEarly access β keystoneapp.dev
Keystone retweeted
The stack behind @keystone_build π
Every tool chosen for one reason: ship a functional prototype fast, without breaking quality. Almost all free tier (0$)
β @nuxt_js v4: opinionated framework, no time wasted on frontend architecture decisions.
β @supabase : PostgreSQL + pgvector + auth in one, zero infra to manage.
β @vercel : CI/CD without configuration.
β @Cloudflare : CDN and security from day one.
β @posthog : product analytics, no setup.
β @MistralAI : synthesis and processing of repository inputs.
β @claudeai sonnet/opus: core product reasoning and high-level technical decisions.
β @resend : transactional emails without managing mail servers.
Didn't pick the most impressive stack, picked the one that lets me focus on the problem, not the infrastructure.
What would you change? π€
Every team loses context. Every agent ships blind.
Keystone fixes that, automatically, from the work you're already doing.
Today I'm launching keystoneapp.dev publicly.
After years shipping for others... today I'm shipping my own.
Here's what it does and why I think it matters π§΅
48





