Fractera Admin

Move to Fractera

Where your existing project comes from — the agent reads it and lays the move out as steps.

The migration mode is not switched on

You can name the source now — but until the mode is on, the agent opens every session as if you were building from an empty page.

Choose the development mode

Name where your project lives today. The agent reads it as a description of what your project does, and lays the move out as numbered steps. Your data moves last, on access you give separately.

Keep the repository open while you are moving. Fractera asks for no token on purpose: a token lying in a settings file is a secret only in appearance. Close the repository again the day the move ends.

What to do next

Tell the agent, in ordinary words, that the move is starting. It reads the project itself — the architecture, the libraries, what rests on what — builds the tree of what your project becomes here, and lays out the queue of steps. You never have to explain your old code from memory.

Your old code is read, never run. Fractera takes the project apart as a description of what it does and builds that meaning again on this architecture. Nothing from the old project is executed on your server, so a broken or hostile dependency cannot ride across with it.

How this works

Where the choice lives. In PLATFORM-CONFIG on the server, beside the development mode. The agent reads it at the start of a session, so it survives the end of a conversation.

The order of the move. The frame goes up first — addresses, tables, sign-in. Then the features, one step at a time, each proved on a live page. Data comes last, on access you give yourself: until that moment a mistake costs almost nothing.

GitHub connection required
en

North America

🇺🇸Englishen

Eastern Europe & CIS

🇷🇺Русскийru

Sub-Saharan Africa

🇺🇸Englishen

Asia Pacific

🇺🇸Englishen