HeraldGoat
SoloHelps people trading financial markets work out when a chart is worth opening.
“I hate being glued to the screen all day, waiting for my setup.”
That’s where HeraldGoat started. I wanted to stop checking the same charts over and over while waiting for the conditions I cared about.
I’m building the product, backend, infrastructure and iOS app myself. It’s still in development. Right now, I’m working out the market-data rights and costs that would let me launch it.
Visit HeraldGoatHow it’s taking shape
- Now · Finding the right data provider
I’m looking for a provider whose licence and pricing make sense for a small launch. Access to an API is one part of that; permission to use the data in a paid product is another.
- Building the system
I built the backend that checks market data against setup rules and saves the results. I also keep the data behind each result so I can see why a setup matched.
- Deciding what belongs in it
I kept coming back to the same question: would this help someone decide whether to open a chart? That gave me a way to decide which features belonged in the product.
- The reason I started
I wanted a way to check for my setups without spending the day watching charts. That became the starting point for HeraldGoat.
How I check for setups
If I change a setup rule, I still need to know which version produced an earlier result. I save those versions so I can investigate a match without guessing what the rule used to say.
I use FastAPI and PostgreSQL to check setups and store their results. Cloud Run and Pub/Sub run the background jobs, which lets me add capacity when there’s work to do and avoid paying for idle servers.