One system
WEBDANGER is the platform. DangerCode is its coding engine; DangerChat is its conversation mode. Accounts, organizations, subscriptions and audit remain unified while the web platform and native engine keep their own source code.
The WEBDANGER platformCode. Publish. Grow.
Product whitepaper · version 2026-10-09. Our architecture, delivery gates and long-term direction in one public document.
From a template to a live project
Choose among 331 templates, inspect the preview, make project changes, run checks and publish a verified version. Version history and rollback are part of the workflow; an AI response alone never proves a successful result.
A Marketplace of useful software
The Registry covers website templates, app starters, UI blocks, dashboards, auth kits, functional modules, integrations, AI skills, workflows and asset packs. Every install requires a pinned version, compatibility, a license, hashes, permissions, tests and rollback.
Five platform tiers
Starter 8, Builder 15, Pro 75, Max 150 and Ultra 500 per month, with fixed EUR and USD catalogues. The annual price equals ten monthly prices, billed upfront. Existing purchased versions keep their terms. AI limits follow measured capacity and budget rather than an unlimited premium-model promise.
Privacy and execution boundaries
Projects belong to their organizations. The native client keeps local work and provider credentials local; hosted execution needs authenticated project scope, sandboxing and limits. Chat does not change files without a coding task. Private customer work never enters volunteer compute.
Members and community
Registrations, managed domains and qualifying annual Members are separate real metrics. Gold, Silver and Bronze preserve issued numbers and cohorts. Community milestones show verified growth and platform achievements.
Partners and creators
Participation will be free. Commissions require verified eligible sales, refund handling, fraud review and append-only accounting. Creator revenue, affiliate commission, compute rewards and Member achievements have distinct rules; no reward arises merely from recruiting another account.
Swarm research
An opt-in research direction: permitted test projects and evaluation jobs on volunteered devices. Computing consent and training-data consent are separate. XP, product credits and any future cryptoasset are different programs. No computing runs silently in a visitor’s browser.
Infrastructure in stages
First measure APIs and a small compute pilot. Next validate regional operations and independent customers. Container sites and a central training cluster follow demand, funding and engineering studies. Distributed regional GPUs are not equivalent to one tightly connected training cluster.
How we demonstrate progress
Delivery is tracked against explicit acceptance criteria. Public counters come from durable platform data. Company scenarios and recurring revenue stay in owner CONTROL. The roadmap is a target sequence through 2030; expansion depends on the published gates.
Explore the roadmap