artahian

7 ms·

1.
Show HN: OpenSoccer – open-source soccer game in browser in 128 prompts(github.com)
3 points by artahian 3mo ago|0 comments
2.
by artahian 7mo ago
Yeah that same experience at our previous startup was one of the main reasons why we started Modelence. We got to a point where we had a dedicated 3-4 cloud platform engineers (out of the 20 engineers total) working full time only on things
3.
by artahian 8mo ago
My previous startup was running on MongoDB since 2014, and after 10 years, 1m+ users and hundreds of enterprise customers everything was just fine.
4.
by artahian 8mo ago
True, usually when I meet people who think so I always ask them what exactly went wrong. One time someone told me: "we just let our frontend engineer build the whole backend and schema and it turned into a disaster and wasn't main
5.
by artahian 8mo ago
Yes - since the framework itself is open-source, you are free to take it and run anywhere you'd like. Of course, the experience is much better if you run on Modelence Cloud since it's zero config and also gives you the dashboards
6.
by artahian 8mo ago
We do have the UI / dashboards, built into the platform - and it's actually one of the most valuable pieces. It's in the second half of the demo video! And great point - while we're focusing on full-stack web apps, I bel
7.
by artahian 8mo ago
Both are hard for complex apps regardless, which is why we’re making sure that the framework has all the necessary guardrails to prevent devs from using it incorrectly. Relational dbs just have more built-in guardrails, but in our case we p
8.
by artahian 8mo ago
MongoDB actually has built-in schema validation which can be enabled, we're just not using it at the moment because we haven't yet found a good use case where the TypeScript schema itself is not enough. The schema in Modelence is
9.
by artahian 8mo ago
The reason why we didn't build a generic platform instead is because everyone already has access to Cursor and Claude Code for building free form applications, and each stack is uniquely different in its challenges. We're picking
10.
by artahian 8mo ago
Nope, but it seems like it's still on a waitlist - are you planning on launching soon?
11.
by artahian 8mo ago
Agree, as for the JS/TS lock-in, we could have applied a similar approach with other languages too, but we intentionally chose to focus on one single stack to create a seamless end-to-end experience instead of providing a generic solut
12.
by artahian 8mo ago
There are often two peak points, one at the beginning when a team has built a frontend, then is looking to add things like authentication and realizes they have to bring in a separate backend (setting things up and connecting is the main fr
13.
by artahian 8mo ago
We had this same challenge in our own app builder, we ended up creating an internal LLM proxy with per-sandbox virtual keys (which the proxy maps to the real key + calculates per-sandbox usage), so even if the sandbox leaks its key it doesn
14.
by artahian 8mo ago
Exactly, and most app builders have realized this and started adding things like built-in auth, cloud, etc, but I still think the right direction is starting with the platform itself and adding the app builder as just one facade for it, rat
15.
by artahian 8mo ago
Yup, the way you interact with MongoDB collections in Modelence is via Store, which has a Zod-compatible schema, enforced at build-time and pre-deployment, instead of runtime (since at that point it's too late).
16.
by artahian 8mo ago
A lot of this is still work in progress, but the key idea is that the framework and the cloud environment have to work together for this, because what you have in the current version of the code has to be compared with what the environment
17.
by artahian 8mo ago
Fair point, although we didn't choose MongoDB just because of schema handling. We've been using MongoDB in production since 2013, so it was a natural choice since we already know a lot more about it than any other database. For th
18.
by artahian 8mo ago
We've been one of the very early Meteor users, since 2013 (our previous startup is featured on their landing page). After about 10 years of scaling on Meteor & Galaxy, we ended up moving Meteor into our own custom AWS cloud because
19.
by artahian 8mo ago
That makes sense, and we've been seeing the same. But in our case, instead of having the LLM inspect an external system, TypeScript is the source of truth for both the schema and everything else, it's all code-defined, so it autom
20.
by artahian 8mo ago
We still have a schema definition in TypeScript, without it things would have been pretty wild actually. But we're doing it in the app layer - in the framework. The schema management idea is that we're adding guardrails around all
21.
by artahian 8mo ago
Great questions: - For extending auth, currently the framework contribution is the main option, but we've intentionally made everything modular so we will be making it extensible with custom external packages as well (or even directly
22.
by artahian 1y ago
I agree - Postgres has been on the rise for the past years, but I think the reason for MongoDB going down in popularity is not reflective of its own progress - MongoDB has only been technically getting better and they’ve recently bought Voy
23.
by artahian 1y ago
Yup - it’s work in progress! We will be adding both shortly.
24.
by artahian 1y ago
If you check our landing page, we have a section where we explain that a bit: https://modelence.com One of the AI-native aspects is if you use the built-in AI SDK ( https://github.com/modelence/modelence&#x2F
25.
by artahian 1y ago
Do you mean real-time data / live sync? It is actually the next thing we're going to release, so yes - it is definitely a core part. We took our inspiration from https://meteor.com and it had a big emphasis on live dat
26.
by artahian 1y ago
Thanks! We do have the auth components here - https://github.com/modelence/modelence/tree/main/packages/au... Probably need to add screenshots also, but our own platform at https://cloud.
27.
by artahian 1y ago
Rails for Ruby is similar with the simplicity and structure (same idea here for TypeScript), but Modelence is more cloud-first focused and less of a pure framework.
28.
Show HN: Modelence – Supabase for MongoDB(github.com)
38 points by artahian 1y ago|14 comments
29.
by artahian 1y ago
v0 and lovable have way too much hype, I think what you're doing with stagewise (i.e. being dev-first instead of optimizing for non-developer users) is the real long term use of AI.