Skip to content

Federación Futuh

Federación Futuh is the layer that shares public data across all active Futuh instances. Instead of each organization independently tracking BOE grant calls, maintaining its own list of sustainable development goals, or drafting standard legal templates from scratch, there is a single Hub Central that does that work once and distributes it to everyone else.

The Hub Central is operated by the Futuh team, within the infrastructure of Asamblea de Cooperación Por la Paz. Your instance connects to that Hub through a daily cron job that downloads updates, stores them in your database, and makes the information ready for modules like Radar, Silvio, or Incidencia Política to use without any additional configuration.

The problem it solves is duplicated work across the third sector. The regulatory bases of BDNS grant calls, the OECD CAD/ODA catalog, Agenda 2030 markers, AECID budget lines, updated data on parliamentarians: all organizations need the same data, and all of them lose hours tracking it down. The federation maintains it once and for all.

The federation works like a wheel with a single hub. At the center, the Hub Central holds the canonical version of each record. At the edges, each Futuh instance consumes that version without sending anything back by default (canonical decision M1 unidirectional). Your instance does not expose your data to the Hub unless you explicitly activate an aggregated service that requires it, which does not happen in v0.1.

This topology has three consequences worth understanding:

  • A single source of truth. When a BDNS regulatory base is updated, the change appears in all federated instances on the next cron run. There are no diverging versions.
  • Zero maintenance cost for you. You do not have to monitor official publications, rewrite templates when regulations change, or keep an ODS list up to date. The Hub does it.
  • Traceability of what comes from outside. Each federated record carries an internal marker (canonical_signature) that lets you distinguish what was synchronized from the Hub from what your organization added manually.

Version 0.1 of the federation covers four categories of canonical data that have been in production since May 2026:

  • BDNS regulatory bases analyzed with AI. The bases for each grant call published in the BOE are processed at the Hub to extract requirements, evaluation criteria, and eligible beneficiaries. Your instance receives the structured analysis, not the PDF.
  • BDNS awards. The historical record of who received which grant, also from BDNS, so that modules like Radar can estimate success rates by grant call.
  • Document templates. Standard agreements, model reports, common legal clause texts (LGPL, GDPR, cooperative contracts). They arrive already drafted in your instance, ready to customize.
  • Silvio Agent Pack. The pre-trained AI agents that Silvio uses for specific tasks (summarizing bases, suggesting clauses, drafting client emails) come from the Hub with their canonical configuration. When an organization proposes an accepted improvement, the Hub incorporates it and propagates it to all.

Each category can be activated or deactivated independently from the client configuration, depending on the sector bundles your organization has subscribed to.

Federación Futuh is not billed by consumption. Access to federated services is included in the annual Futuh subscription your organization pays (calculated from your triennial income on the futuh.coop pricing page). There is no download limit, no surcharge for the number of grant calls tracked, and no per-template fee.

The reasoning behind this model: if the federation delivers on its promise (canonical data maintained by us, you focus on your work), there is no sense in charging you for using it. That would be a barrier to adoption of the service that funds the subscription. It is a deliberate decision of the Futuh canonical project: the code is free and downloadable without federation; federated services are the filter that distinguishes the subscription from a bare installation.

The federation is transparent day to day: you do not see it. What you see are modules that work because there is data behind them.

  • Radar consumes BDNS regulatory bases and awards to score suitability.
  • Silvio consumes the Agent Pack for its pre-trained AI tasks.
  • Incidencia Política consumes parliamentarian data for each contact’s profile.
  • Gestión de ayudas uses federated document templates as a starting point.

If your Futuh instance stops federating (for example, because you do not renew your subscription), the modules continue working with the last data they synchronized, but they no longer receive new canonical updates.

The Federation is the module from which everything arrives that your organization does not have to maintain: regulatory bases, templates, AI agents, vocabularies. It produces no value on its own; it delivers it to the rest. Radar consumes the canonical bases and awards to score fit; Silvio receives the Agent Pack with its canonical configuration; Plataforma de Recepción Inteligente works from federated document templates; Incidencia Política draws on IATI/ODS vocabularies and European Parliament data maintained at the Hub. When your instance synchronizes, all those modules are brought up to date without any intervention from you.

ModuleWhat this module gives / receivesFlow
RadarReceives canonical regulatory bases + awards from the HubSynchronize with the Federation
SilvioReceives canonical Agent Pack + prompt templates from the HubSynchronize with the Federation
Plataforma de Recepción InteligenteReceives canonical document templates from the HubSynchronize with the Federation
Incidencia PolíticaReceives IATI/ODS vocabularies + European Parliament data from the HubSynchronize with the Federation