Self-hosted low-code + open LLMs (DeepSeek/Qwen/GLM): real enterprise apps in 5 min

A developer has demonstrated how pairing open-weight LLMs like DeepSeek V4, Qwen, and GLM with the self-hosted, open-source Oinone metadata-driven low-code framework can produce maintainable enterprise business applications in minutes. The approach allows AI to operate directly on business metadata rather than generating throwaway code, enabling natural-language app creation, record queries, and approval workflows while keeping data on-premises. The developer reports that this metadata-driven method reduces token costs by approximately 60% compared to verbose code generation.

In 2026, open-weight LLMs got good — and pairing one with a self-hosted, open-source, metadata-driven low-code framework is how you turn that raw intelligence into a real, maintainable business app. DeepSeek V4, Qwen, GLM are catching or beating the closed frontier on price and many tasks, and you can run them yourself. But there's a gap between "the model is strong" and "the model is doing real work inside a maintainable business application." This is a short take on closing that gap. A lot of teams think "enterprise AI = add a chat box." But the value is in letting AI understand your business, operate your data, and trigger real actions — create a model, generate an app, run an approval, query records. That requires the AI to be not a bolt-on, but to share the same metadata as your business. Oinone https://github.com/oinone/oinone-pamirs is 100% metadata/model-driven for exactly this: AI works at the metadata layer and produces maintainable, auditable output instead of throwaway code. curl -L https://gitee.com/oinone/oinone-docker-shared/raw/master/oinone/docker-compose.yml -o docker-compose.yml docker compose -p oinone up -d open http://127.0.0.1:88 admin / admin Oinone's agent platform Aino supports model access — point it at DeepSeek/Qwen/GLM via API, or a locally-deployed copy for data-sensitive cases nothing leaves your perimeter . Notes: With the model wired in, ask the AI to generate a CRUD business app in natural language, and look at what it produces: That's the line between "AI-native" and "a low-code tool with a chatbot." Open LLMs are strong enough. What's missing is a foundation that turns them into apps an enterprise can actually run. That's the bet. Bottom line: an open LLM gives you intelligence; a self-hosted, metadata-driven low-code framework like the open-source Oinone gives you a maintainable, auditable app around it — and because the AI writes compact metadata, not verbose code, token cost drops ~60%. Q: Which open LLMs can I use? Any — DeepSeek, Qwen, GLM, etc., via API or a locally-deployed copy. The model sits below the metadata layer, so it's swappable without changing your business logic. Q: Can I keep everything on-prem for sensitive data? Yes. Run the LLM locally and self-host the framework open source, AGPL-3.0 ; data never leaves your perimeter. Q: How is this different from adding a chatbot to a low-code tool? The AI operates on the same metadata as the runtime and outputs a reviewable, revertible metadata diff — not throwaway code bolted onto a chat box. If this resonates, a ⭐ helps more developers find it: