Fractera

All project settings in one place

Languages, name, search, header, footer and twelve feature switches live on one screen. Save once, and every connected application takes the change in seconds, without a rebuild.

OpenSource Web4 agent & app starter kit

How a setting goes

  1. The architect changes it

    On this element’s pages, in one of eight groups, and saves.

  2. CONFIG keeps it

    In APP-CONFIG and PLATFORM-CONFIG, written as a patch, never overwritten.

  3. A signal goes out

    Every subscribed application gets it the moment you save and takes the new settings itself.

  4. Pages show it

    The application applies them over its own defaults, and visitors see the change after reloading.

In a single project every element takes its settings from here; in an app factory a new element keeps its own.

On, asleep only when memory is short

The element starts with the node. With less than 0.5 GB of free memory the node may put it to sleep; the first call or a calendar entry wakes it in seconds, and above 1 GB free it comes back by itself.

What changes for you

Without itWith CONFIG
Settings scattered across the repositoriesAll settings of the project on one screen
A rebuild for a menu item or a switchA save, and every connected application follows in seconds
Each application decides alone what to showTwelve switches, from the top menu to the language switch
An application stops without its settings serviceEvery application keeps its own settings and runs without CONFIG

Change this project's settings

This page is a working tool as well as a description: languages, the title, search, the header, the footer and twelve switches change on this element's pages, and every connected application follows within seconds, with no rebuild.

Only the architect can change them, after signing in. Visitors never see these pages.

Open the project settings →

Twelve switches

Each one turns a feature of every connected application on or off:

  • Top menu · cookie banner · sign-in
  • Questions and answers · page width · social networks
  • Footer pages · offline copy · breadcrumbs
  • Theme switch · language switch · width and design-skill indicator

Eight groups, each on its own page

Languages
Which languages the project speaks and which one is the default
Basics
The name of the project, its description and contacts
Search and AI
How search engines and AI assistants read the project
Meta and media
Logos, icons and the pictures shown when a page is shared
Parallel routing
Which parts of the application screen are shown side by side
Header
The menu at the top of every page
Footer
The links and pages at the bottom of every page
Cookie banner
The consent message and its words in every language

Your applications run without it

CONFIG is an addition, not a foundation. An application that connects over MCP gets one place where all its settings change; only the architect changes them, after signing in, and applications read them with the node’s key.

Your own builder comes with it

Every element of the node comes with its own Claude Code agent and can get its own Telegram bot. When something in this element should change, write to its bot from your phone, and the agent updates the logic or the design.

The agent works only in its element's folder and never reads the whole node, so each change costs fewer tokens. Your Claude Code subscription pays for it.

  • The element's bot is connected in the core, on its «Telegram» page.
  • The agent returns a commit; you look at it in «Preview» and accept it or turn it down.
  • At the computer, the agent's terminal is in the core, in this element's «Build».

Open source

Built by Fractera for the Lagrix protocol and for any web2 project with more than one application. MIT license, the code is at github.com/Fractera/fractera-config-starter.

GitHub →

Questions and answers

Does an application need CONFIG to run?
No. Each application keeps its own settings and works without it; CONFIG gives one place to change them all.
How fast does a change arrive?
On save every subscribed application gets a signal and takes the new settings; visitors see them after a reload.
And in an app factory?
A new element keeps settings of its own; in a single project every element takes them from here.