What should Keryx prioritize next?

[evantahler]

Keryx is pre-1.0 and the roadmap is still flexible. I want to build what the community actually needs, not just what I think is cool.

Here are some directions I'm considering — which ones matter most to you?

• More MCP capabilities — streaming responses, resource subscriptions, prompt templates
• Database flexibility — support beyond PostgreSQL (MySQL, SQLite, etc.)
• Deployment guides — Docker, Railway, Fly.io, AWS recipes
• Auth patterns — JWT support, API keys, OAuth provider integrations
• GraphQL transport — actions as GraphQL resolvers
• Rate limiting improvements — more granular controls, sliding windows
• Plugin/extension system — shareable bundles of actions + initializers
• Better error handling DX — error boundaries, retry patterns
• Performance benchmarks — published comparisons with other frameworks

Feel free to suggest something not on this list. What would make Keryx more useful for your use case?