How crayy works
You build finance tools. We put them somewhere they actually get used.
The ecosystem effect
You know what happens when you deploy a finance app to Vercel or Railway? Nothing. It sits there. You do all your own marketing, all your own distribution, beg people to try it.
Crayy works differently because apps here feed each other. Someone builds a screener, someone else builds an earnings analyzer, a third person builds a portfolio tracker. A user comes in through the screener, finds the earnings tool, ends up on the tracker. Each app is pulling users toward the others without anyone coordinating it. The more apps on the platform, the stickier the whole thing gets.
Same thing on the data side. Apps share a surface. A momentum signal from one tool becomes an input for another. You don't have to build the whole stack yourself because other people are building the pieces around you.
Agent-native by default
Every app you deploy here gets an entry in a single discovery endpoint: GET /api/discover. That's it. That's the whole integration.
When an AI agent needs to do something with finance data, it hits that endpoint, sees what's available, and picks the right tool. Your app is in the mix automatically. You didn't write a plugin. You didn't register for a marketplace. You didn't implement OAuth. You just deployed, and now agents can find you.
Think about what this means. Every agent-powered finance workflow that touches crayy can route to your app. You get distribution from a channel that literally did not exist two years ago, and you didn't do anything extra to get it.
Your economics
We don't take a cut. No rev share, no platform fee, no "free tier with limits that conveniently push you to pay us." You charge what you want, keep what you charge.
Why? Because we're not trying to be a payment processor or an app store. We want the ecosystem to be big enough and good enough that being the infrastructure underneath it is the business. Your success is the product.
How deploying works
Tell your AI agent "read mvp.crayy.com/deploy and deploy this" and go get coffee.
The agent reads our deploy docs, packages your code, and ships it. On our end: we detect what kind of app it is, run an AI review to catch anything sketchy, build a Docker container, health-check it, and wire it into the platform. About two minutes, start to finish.
You don't make an account. You don't configure anything. You don't set up CI. Node, Next.js, Flask, FastAPI, Streamlit, Gradio, static sites. Just send the source code and we figure out the rest.
Get in early
The platform is live right now. Still early. That matters for a few reasons.
- Names are first-come.
mvp.crayy.com/screeneris a hell of a lot better thanmvp.crayy.com/yet-another-screener, and once it's taken it's taken. - Fewer apps means more eyeballs on each one. The people deploying now are going to be the ones everyone else sees first.
- You shape what this becomes. Early apps set the tone. If you build something good now, the ecosystem grows around it.
"read mvp.crayy.com/deploy and deploy this"
→