What Demostatics Is

Demostatics is an investment company operating on its own information platform. The platform is a centralized, continuously updated hub that aggregates fragmented global data and turns it into structured, statistically usable intelligence for risk analysis and investment decisions. The company sells that intelligence, advises on it, intends to manage capital with it and to trade its own book with it. See Business Model.

The one-sentence definition

Demostatics gathers world data from many sources into its servers, refines raw inputs into analysis-ready data, and sells access to the result.

Everything else on this site is an elaboration of that sentence, or an honest accounting of which half of it is implemented.

That sentence describes the platform, and it is no longer the whole company. The same refined data is meant to feed the firm’s own advisory calls, its managed portfolios and its own trading book, which makes the platform both a product and internal infrastructure.

What it covers

The platform’s declared subject matter is the state of the world, in five broad layers.

Layer	What it means	Status
Organizational and geopolitical structures	Institutional and state-level structure, for a view of global dynamics	Planned
Worldwide local news	Local reporting captured continuously so emerging developments surface in time	Planned
Traffic and infrastructure	Land, air and sea movement — road networks, flight paths, maritime routes	Planned
Ecological conditions	Weather shifts, land-use change, ecological disruption, and how regions change over time	Planned
Meta-descriptive listings	Structured, context-rich records generated from all of the above	Planned

Nothing above is gathered yet

These are the categories the founding specification commits to. No ingestion of any kind runs today. The two tables meant to hold this data — reports and database_items in demostatics-web — exist and are queryable, but their rows are written only by local seeders. See Worker Tier.

What it produces

Three things, in increasing order of processing:

Reports. Worker-produced summary rows — a title, a summary, a place, a category and a publication date. Filterable by geography, category and date range, and exportable to Excel, Word, CSV and JSON. The listing and the export are Shipped; the rows have no producer.

Database items. Worker-produced current values — the latest measured figure for a subject in a place. Same filters, ordered by measurement time. Shipped as a surface.

Caution

database_items.value is a text column holding a display string such as 48,210 MW, with a single measured_at and no history table. It is never cast to a number. That is why there is not a single chart anywhere in the product, and cannot be until the roadmap’s Phase 2 introduces real time series.

Risk-focused views. Views built for decision-makers that surface vulnerabilities, emerging threats and regional dynamics. Partial — the desktop client computes a real composite risk score locally from whatever data it receives, but it receives it from a mock server, not from Demostatics.

What a customer buys

The business model has four lines, all Planned. Only the first has any code behind it.

#	Line	What is sold	Status
1	Data and intelligence	Structured data, risk views, reports and API access, by subscription — for individuals, enterprises and partners integrating the data into their own systems	Planned — the platform surfaces exist, nothing is sold
2	Investment advisory	Recommendations, research, model portfolios, signals	Planned — licensed activity, nothing built
3	Discretionary management	Client capital managed on the client’s behalf	Planned — licensed activity, nothing built
4	Proprietary trading	Nothing — the firm trades its own capital	Planned — nothing built

Line 1 is the original business and the only one with implementation behind it: the listing, filtering and export surfaces described above. Even there, nothing is sold — no subscription, plan, entitlement or billing table exists in any repository. Lines 2, 3 and 4 are licensed activities with no implementation of any kind in any repository, and no licence to conduct them. See Business Model for what each line is and what it requires.

Within line 1, the desktop client’s contract names four tiers — free, individual, pro, enterprise — and nine gate-able features. That vocabulary exists only in Rust, and only against a mock server. See Stream Contract v0.2.

No prices exist

No pricing, tier names, tier count, currency or market sizing appears in any founding document. “Tiered plans” and “higher-tier subscriptions” are the entire specification, and there is no pricing of any kind for lines 2, 3 and 4.

What it is not

Being precise about the boundaries matters more than usual here, because several documents inside the project get this wrong.

• Not a data vendor reselling a feed. The claim is refinement — raw inputs in, analysis-ready structure out — with pricing that scales to how much data was gathered and how much statistical work was done.
• Not a single application. It is four codebases: a web display tier, a desktop analytics client, a mobile client, and a worker backend. See Where Everything Lives.
• Not a trading or money-moving system today — but that is now the intent. The firm intends to manage client capital and to trade its own book. None of it is built: no order, position, portfolio, custody or money schema exists in any repository, and there is no legal entity, no licence and no compliance function. It is gated on licensing rather than on engineering, and licensing is the longest-lead-time item on the roadmap — months to years, and no amount of engineering shortens it. See Regulatory Posture; nothing there is legal advice and every item on it needs counsel.
• Not, today, a system that gathers anything. demostatics-web’s own README says it plainly: “This repository does not gather or process anything.” Neither does any other repository.

The old “never take custody” advice is superseded — its reasoning is not

Earlier documents recommended never holding client funds and keeping money schema out of the repository. That recommendation is overridden by founder decision. The reason behind it still stands: a half-designed money schema is a liability the day it merges rather than the day it is used. Design the money layer against a real licence and a real custodian, not against a guess.

The community half

Demostatics is not only a data product. A forum, polls and an editorial layer sit alongside it, and unusually, they are the most complete part of the platform.

Surface	Status
Forum posts, threaded comments, communities, search and sorting	Shipped
Polls with voting and comments	Shipped
Accounts, email verification, profiles	Shipped
Role-based moderation and bans	Shipped
Editorial news and About Us articles	Shipped

The stated intent is that forums act as editorial spaces: users vote on topics or on contributors, and Demostatics invites selected contributors to give authoritative input. The voting mechanics exist; the invitation model does not. See Who It Is For.

Next

• Why It Exists — the problem this is a response to
• How It Works — the architecture in one page
• Where Things Stand — what is actually built