Q: How can I contribute?

PRs and bug reports are welcome on the public repos: LEGIONGASPER, LEGIONHERCULES and legionnative. Check each repo's contributing notes before opening a pull request. For the platforms whose repos are no longer public (DEATHBASE, legion-cloud), feedback runs through their live consoles.

Q: How is this site related to apply.deathlegion.site?

They are two halves of the same collective. deathlegion.site is the open-source portfolio — the tools, the repos, the network. apply.deathlegion.site is the recruitment platform: the application pipeline, member directory and the OAuth2 identity provider behind every DL ID. Every 'Apply to Team' button on this site links there; everything documented here is readable on GitHub, no application required.

Question 1

What is Death Legion Team?

Accepted Answer

Death Legion Team is an open-source group from Sri Lanka (Colombo), operating as DEMO × HEXA. The GitHub profile — deathlegionteamlk — currently counts 66 public repositories and 129 stars: agents, OS kernels, a homemade programming language, emulators, and the documented six-tool portfolio introduced here. The profile bio says it straight: building things nobody asked for since forever.

Question 2

What is DEMO × HEXA?

Accepted Answer

DEMO × HEXA is the team's working alias from the original deathlegion.netlify.app site — the era that documented the six-tool portfolio. It's not a marketing invention: the legionnative README still credits 'DEMO X HEXA × Death Legion Team'. This site is the continuation of that era, rewritten so every claim matches what is verifiable today.

Question 3

Are the projects really free?

Accepted Answer

The three public repos — LEGIONGASPER, LEGIONHERCULES and legionnative — are MIT licensed: fork them, modify them, use them commercially. The origin site's promise for all six was MIT with zero API fees. DEATHBASE and legion-cloud run today as live platforms with free entry tiers (legion-cloud advertises $200 in free credits); their code is no longer public, so we say so instead of pretending.

Question 4

Is LEGIONHERCULES really 100% local?

Accepted Answer

Yes. Inference runs through Ollama on your hardware — the README's own words: no API key to generate, no billing page to visit, no usage cap to hit. You pull a model once (llama3.2, codellama, mistral, llama3.1 and phi3 are named in the docs) and it stays on your machine. You can verify the claim yourself with three commands: ollama serve, ollama pull, legionhercules chat.

Question 5

What can LEGIONGASPER do that a single agent can't?

Accepted Answer

Coordination. Per the README: you give it a task, it splits that task into pieces, hands each piece to a specialized agent, runs them in parallel, and stitches the results back together — the captain-agent pattern. On top of that: five-layer memory down to a ChromaDB vector store that survives reboots, Redis-backed distributed memory, an agent factory, governance and audit logs, and a live WebSocket dashboard on localhost:8080.

Question 6

What is DEATHBASE built on?

Accepted Answer

Cloudflare's edge. The live platform describes itself as the open-source Firebase alternative: a SQLite database, a full auth system, REST + GraphQL APIs and realtime streaming, with AI Studio and Vault added in v2.0. Honest note: the code repository is no longer public — the deployed platform at deathbase.pages.dev is live and is the source of truth.

Question 7

What happened to legion-virtual?

Accepted Answer

It's the one entry we document as an archive. The origin site described WASM-sandboxed dev environments — sub-2s spin-up, no Dockerfile, offline-capable — but the repository is no longer public and the old legion-virtual.pages.dev URL now hosts a different product (Legion Mail). Its dossier on this site is labeled origin-documented, and the features carry an asterisk for exactly that reason. We'd rather show a labeled archive than a fake demo link.

Question 8

What does legionnative target?

Accepted Answer

Android, iOS and web from one codebase — TypeScript runtime, Rust core for native ops, Vite-powered HMR, Skia rendering and a WASM plugin system. The repo's numbers-not-marketing table sets the targets: cold start <100ms, hot reload <50ms, base bundle <50KB, memory <20MB, full offline. It's v0.1.0 — early, and measured against those targets in public.

Question 9

How can I contribute?

Accepted Answer

PRs and bug reports are welcome on the public repos: LEGIONGASPER, LEGIONHERCULES and legionnative. Check each repo's contributing notes before opening a pull request. For the platforms whose repos are no longer public (DEATHBASE, legion-cloud), feedback runs through their live consoles.

Question 10

How is this site related to apply.deathlegion.site?

Accepted Answer

They are two halves of the same collective. deathlegion.site is the open-source portfolio — the tools, the repos, the network. apply.deathlegion.site is the recruitment platform: the application pipeline, member directory and the OAuth2 identity provider behind every DL ID. Every 'Apply to Team' button on this site links there; everything documented here is readable on GitHub, no application required.

FREQUENTLY ASKED QUESTIONS

READY TO BUILD?

FREQUENTLY ASKED QUESTIONS

01What is Death Legion Team?

02What is DEMO × HEXA?

03Are the projects really free?

04Is LEGIONHERCULES really 100% local?

05What can LEGIONGASPER do that a single agent can't?

06What is DEATHBASE built on?

07What happened to legion-virtual?

08What does legionnative target?

09How can I contribute?

10How is this site related to apply.deathlegion.site?

READY TO BUILD?