[huntergemmer]

Thanks! The name was honestly just "what does this do" + "how does it do it" haha.

Interesting you mention three.js - there's definitely overlap in the WebGPU graphics space. My focus is specifically on 2D data visualization (time series, financial charts, dashboards), but I could see the rendering patterns being useful elsewhere.

On sustainability - still figuring that out. For now it's a passion project, but I've thought about a "pro" tier for enterprise features (real-time collaboration, premium chart types) while keeping the core MIT forever. Open to ideas if you have thoughts.

Appreciate the kind words! :)

[PxldLtd]

Have you thought about leaning into some of the fintech space? They'd happily pay for the sorts of features they need to stream financial data (which is usually bazillions of data points) and graph it efficiently.

Off the top of my head, look into Order Book Heatmaps, 3D Volatility Surfaces, Footprint Charts/Volatility deltas. Integrating drawing tools like Fibonacci Retracements, Gann Fans etc. It would make it very attractive to people willing to pay.

[huntergemmer]

Absolute gold comment here :)

This comment was buried yesterday. I'm sorry for the late response!

I was thinking about a pro tier for this kind of specialized stuff. Core stays MIT forever, but fintech tooling could be paid.

Of the chart types you listed, is there a preference for what gets done first?

Order Book Heatmaps first?

[PxldLtd]

No problem :) I asked a friend who's a bit closer to the space and he agrees, definitely Order Book Heatmaps. The speed you're getting would make this a killer feature.

Competitors typically have to snapshot/aggregate because their graphing libraries are heavily CPU bound. Being able visualise level 2/3 data without downsampling is a big win. Also being able to smoothly roll back through the last 12hrs of tick-level history would be really neat too.

I'd say the bare minimum feature set outside of that is going to be:

- Non linear X axis for gaps/sessions

- Crosshairs that snap to OHLC data

- Logarithmic scales, Candlesticks, Heikin-Ashi, and Volume profiles

- Getting the 'feel' nice so that you can quickly scale and drag (people are real sticklers for the feel of these tools)

- Solid callbacks for events for exchange integration, people hate leaving their charts to place an order eg (onOrderModify etc)

- Provide a nice websocket data ingestion pipeline

- Provide an api so devs can integrate their own indicators, some sort of 'layers' API or something.

Sorry if I can't be of more help as I'm just a hobbyist in this area!

[keepamovin]

hunter that's why your licensing is super important. If you don't lock it down you are doing free R&D for giant firms who have the money to make you, but will just rip you off if they can. I speak from extensive OSS experience. The feelgood of giving away wears off, make the right choices with regard to IP and you can capture the value you are creating for people who use it.

[PxldLtd]

This is a really good point. Competitors in this space have a lot of resources so there's a tightrope to walk if you go the OSS core route. Any of these competitors could leverage your core and provide many more features than you could reasonably implement.

BSL/BUSL seems like a good fit for licensing here. It's technically source available instead of open source but just adds the layer that a competitor can't be built using your core. Otherwise the core is free to modify and fork. AGPL might be an option but I fear it would scare off a lot of companies in the space who have policies against AGPL licensed code but you'd get to keep advertising as OSS.