epanet-js VS saasform

At the start up I work at [0], we use an open source library I developed to run hydraulic models of water networks in JavaScript [1].

A hydraulic model may be between 1-10MB and the simulation results can end up being 100+MB of time series data.

Other vendors with proprietary engines have to scale up servers to run their simulation engineers and will store and serve up results from a database.

Having everything done locally means we only have to store a static file and offload the simulation to the client.

Because we've architected it this way our hosting costs are low and users generally have faster access to results (assuming they're running a moderately decent machine)

[0] https://qatium.com/

[1] https://github.com/modelcreate/epanet-js

I'm a civil engineer and I wrote an open source library that compiled a C library to javascript for my own personal projects - epanet-js [1]

A water utility in Spain spun off a start up called Qatium [2] and they used my library as the engine of their simulations and asked me to join.

[1] https://github.com/modelcreate/epanet-js

[2] https://qatium.com/

I created a handful of application around water engineering/modelling [1], plus an open source library to run the simulations in javascript [2].

A water utility in Spain spun off a start up to create a similar web based water modelling application and they used my open source library.

They approached me and I joined them and have been able to maintain the open source library as part of my role.

[1] https://github.com/modelcreate/epanet-js#featured-apps

I work as a water engineer, specializing in building hydraulic models so water utilities can simulate their network.

A big part of that is calibrating them which can be time consuming, you look through hundreds of options. I create a few web based apps to help grind through these tasks but ultimately they were for my own use as a consultant to close projects quickly.

I did pull out the engine as its own open source library for other to use, and that ended up helping me get my current role where I can now maintain it and be paid at the same time.

https://github.com/modelcreate/epanet-js

https://github.com/modelcreate/epanet-js

I've built a few open source apps and few other little projects to help automate my workflow.

There are only a handful of providers of modelling software, most are commercial and one recently sold to Autodesk for $1B.

Not sure I'll convince the industry to change but I'm enjoying tinkering around and making my own small difference.

Saasform: https://github.com/saasform/saasform

I had to prioritize another project (solokeys).

I still really believe both: 1) in an open source alternative to auth0, 2) in combining auth+payments for saas.

However, because they’re two problems, it’s probably best to focus on just one. For me trying to launch Saasform the issue has been to find and onboard customers quickly and at scale.

I also purchased Landkit, but eventually found it very heavy. I then essentially remade it on top of Fresh [1]. Code is here if anyone needs it [2].

[1] https://github.com/cssninjaStudio/fresh

[2] https://github.com/saasform/saasform/tree/main/data/themes/f...

If it's a web saas, we're building Saasform [1] with your use case in mind.

One relevant example is launching your MVP as a serverless API (e.g. on Firebase) + react/vue front end. Just iterate on your core product and features, we handle home page, registration and payments.

For mobile apps I'd recommend Expo [2] and, if you can, stay with their managed flow. If you want to iterate fast, you need to take into account the time to release to the stores and Expo can help with that. Similarly as for the web, I'd look into a serverless API model to start.

For email notifications I'd go with Sendgrid.

I personally never used no-code solutions but different people recommended Bubbles [3].

[1] https://saasform.dev

[2] https://expo.io

[3] https://www.bubbles.io

Starter kit to "transform your project into a SaaS", with auth+payments.

https://github.com/saasform/saasform

Saasform: shameless plug, this is my project, modern (at lease I hope), written in typescript

We are also doing something like that lol. It's a crowded field I see. Of course any cross contamination of PR is more than welcome :-)

I made this exercise to guide myself throught the process of starting from a list of features, summarizing benefits, prioritize them, sparkle some keywords and finally output a marketing page.

Working to make a marketing/public site for a micro-saas I was building, I realized there's plenty of articles about the structure of the landing page, sticky header, include quotes, etc. but there's little on how to actually write the content. I worked w/ different marketing professionals in the past and, though everyone has their own style/processes, the tldr is "talk about benefits, not features".

If you're making a marketing page, I hope you can find it useful too!

Please lmk if 1) the exercise makes sense to you, 2) the format is clear/unclear - what can be improved, 3) should I maybe write an accompanying blog post? other ideas?

For context, I expect to launch a number of micro-saas in the next months, so I wanted to build a repeatable process. I then plan to run all these sites out of config files like this [1].

[1] https://github.com/saasform/saasform/blob/main/data/config/w...