3 ms·
You can take it a step further and strip out the frontend. Honestly. Nobody needs it and if you need any UI stuff it in the MCP. This is what I did with this p
by _pdp_ 4mo ago
You can take it a step further and strip out the frontend. Honestly. Nobody needs it and if you need any UI stuff it in the MCP.
This is what I did with this project https://github.com/crmkit/crmkit/ https://github.com/crmkit/crmkit/ and to be honest the approach grows on me and fits well if you are a backend person.
- spiderfarmer 4mo ago"Nobody needs it" "Fits me well" So maybe don't speak for everybody?
- re-thc 4mo ago> You can take it a step further and strip out the frontend. You can take it a step even further and strip out all the code too!
- subscribed 4mo agoI need it, I want it. Why speaking out for me?
- mcbetz 4mo agoI like the direction! But why stop with CRM functionality with very limited schema for tasks on the headless when OP has a lot more to offer there? Why stop at CRM plus Project Management then? Why not also schemas for ERP, HR, finance tools and all other business software? And we even bother with a custom made API when PostgreSQL and PostgREST could reduce the full thinking to the database schema?
- theturtletalks 4mo agoI’m actually building an open-source Shopify for every vertical. The schema for each vertical is different and we are using Postgres. It comes with a built-in AI that you can ask to add new products, change prices, etc. The next evolution for this is to allow users to use the AI to change the database schema itself. Like if someone is using our restaurant software and wants to start selling merch. I’d want them to be able to use the AI to change the database schema and add products and shipping from the e-commerce one. I really do think that is the future of SaaS. You start from a base SaaS and the AI customizes it to your business over time.
- hashmap 4mo agoyou can, yes, and the db becomes model weights that you can just use lookups for retrieval and have attention live in vram.