YecoAI

Ender-1

Our AI model for EnderDevelopment, a fine-tune of Qwen2.5-Coder-1.5B (Apache 2.0). It is used only inside the product and is not publicly available.

Correction note: an earlier version of this page described Ender-1 as a fine-tune of Qwen2.5-Coder-3B. After clarifying the license, the 3B model turns out to be distributed under a non-commercial license: Ender-1 is therefore based on the 1.5B model (Apache 2.0). Details in the full correction.

Ender-1 is the proprietary code model behind EnderDevelopment: a heavily optimized fine-tune of Qwen2.5-Coder-1.5B, trained on EnderDevelopment's own usage data. It is not a general-purpose model and not part of the Yeco LLM Series, which remains fully proprietary: Ender-1 inherits Qwen's Apache 2.0 base and specializes it for one job, turning gaming community intents into working Minecraft plugins, FiveM scripts, Discord bots, and valid server configs. It will never be released as open weights or via public API: Ender-1 ships exclusively inside EnderDevelopment, and this article documents what it is, how it was built, and its rollout plan.

What Ender-1 actually is

Ender-1 starts from Qwen2.5-Coder-1.5B, a small code model released under Apache 2.0, and adapts it with a two-stage recipe: continued pretraining on EnderDevelopment's code-and-config distribution (Spigot/Paper Java/Kotlin plugins, plugin.yml, permission trees, BungeeCord/Velocity YAML/JSON, FiveM Lua, Discord bot sources), followed by instruction tuning on intent-to-artifact pairs from the platform's real traffic. The result is deliberately narrow: where the base model is a general code assistant, Ender-1 is a specialist in the exact stacks and request shapes EnderDevelopment serves.

The distinction matters. The Yeco LLM Series models (Yeco-PII, Flash Mini-IT) are trained from scratch or on our own pipelines and are fully proprietary. Ender-1 is a different category: a fine-tune of an excellent open base, optimized and evaluated so tightly that it beats larger generalists on its home turf. Vertical data and tight evaluation beat raw scale in a narrow domain, the same principle behind Yeco-PII outscoring models 5.4 times larger on PII detection.

The data loop, under policy

The fine-tuning corpus comes exclusively from EnderDevelopment's free tier, under the platform's standing policy: de-identified prompts and accepted generations, no account identifiers or payment data, filtered third-party copyrighted assets, account-level opt-out honored in every training snapshot. The prompts already processed by the platform are the seed; the compounding loop (more users, more intents, better model, better generations) is the actual asset.

Base model
Qwen2.5-Coder-1.5B
Fine-tune, not a from-scratch model
Platform registered users
30K+
The data loop behind Ender-1, updated continuously

Internal by design: no open weights, no public API

Ender-1 will not be released as open weights, will not be served through a public API, and will not be licensed: it runs only inside EnderDevelopment. The reasons are practical, not ideological. The model's value is inseparable from the platform's verification pipeline (compile checks, config validation, functional tests), so serving it standalone would strip away exactly what makes its outputs reliable. Releasing it would also hand competitors the distillation of our most valuable dataset. EnderDevelopment has always used European models for its pipeline, Codestral Latest among them, and Ender-1 is the step where the platform's own proprietary model takes over that role.

Rollout: staged, reversible, product-anchored

Ender-1 rolls out to EnderDevelopment users in stages, with the previous pipeline kept as fallback at every step and as permanent verifier for what Ender-1 produces. Ender-1 is available only inside EnderDevelopment. The structure:

  • Stage 1 (current), Premium users only: Premium accounts can opt in and use Ender-1 first, while the production pipeline remains the default for everyone else.
  • Stage 2, new free users: once quality metrics hold on Premium traffic, the rollout extends to newly registered free accounts.
  • Stage 3, all users: general availability across the platform, with the previous pipeline retained as verifier of Ender-1's output.
  • Throughout the rollout, Ender-1 can be updated or improved at any stage to assess whether it can fully replace the previous pipeline, a decision made on measured generation and functional pass rates, not on schedule.

Every Ender-1 output is compiled, packaged, and functionally checked before reaching a user, the same dual-LLM discipline that guards DeskNexo: Ender-1 proposes, the production pipeline verifies. Regressions surface within hours because the evaluation set is the platform's own traffic.

Limitations and honest scope

  • 1.5B parameters: encyclopedic knowledge and long-chain reasoning remain out of scope; the model is a vertical code generator, not a general assistant.
  • Training corpus is gaming-domain specific; performance outside Minecraft/FiveM/Discord/infra stacks is untested and unsupported.
  • Being a fine-tune of Qwen2.5-Coder-1.5B, it inherits that base model's licenses and failure modes; the Apache 2.0 notice applies to the base, the fine-tune stays internal.
  • Beta software: outputs can be wrong, incomplete, or subtly broken; platform verification and human review remain part of the loop throughout the rollout.

Next steps

The agenda follows the rollout: publish aggregate quality metrics from each stage (generation success, functional pass rates by category), iterate checkpoints on a fixed cadence as the corpus grows, and decide on schedule whether Ender-1 replaces the previous pipeline outright. Ender-1 is the first YecoAI model born from a live product, and the template for how our data engine works: real usage, governed by policy, compounding quality.

Distribution first, data from real intents, evaluation by compilation. Ender-1 is what a product-trained fine-tune looks like when the loop closes.

Related content