Do I need to know how to program?
No. The agent assembles pages from your words: you describe what a page needs, and it builds the page from ready-made blocks. Programming is only needed for dynamic blocks that compute data — and even that is handled by the agent. From you it only takes the knowledge of which numbers you want to show and where they come from.
Who edits the portal pages?
The managing AI agent. People do not edit content in a browser: the interface has no editor, only page viewing and commands to the agent. This is deliberate. The content lives as plain files under git — a version store — so every edit is visible and an unlucky one can always be rolled back. There are also never two “latest” versions of a page, or changes nobody can attribute.
Do I need Xedant Agent?
Yes, if you want the chat and edits in plain words: the agent connects by address and key, after which you can say “add a contacts block to the home page” — and it will do it. Without it the portal still works: pages and the tree are visible, the public site opens, dynamic blocks compute. Only the agent chat is hidden. Details are in the Chat with the AI Agent section.
How is this different from WordPress and ordinary content management systems?
The content lives as files in git and is fully controlled by an agent, not a person: the interface simply has no editor. Pages are assembled from 27 block types, and some blocks compute data with Python scripts — the numbers on the page are live, not typed in by hand. Ready-made systems are convenient for hands-on edits, but they require someone to make those edits. Here you describe in words what you need — and get a page. More about the website product is on the WordPress Agent page.
Where is the data stored, and can everything be moved?
On your server. The service data (the database, the license, unread marks) lives in the permanent /apps/portal volume, while the portal content itself is in a separate /project/apps/portal folder. The content is plain files: the folder can be kept in git whole and moved to another server by copying. No export or import is needed, and the data is not tied to the program. Details are on the Installation page.
Where should keys and fine-grained settings be kept?
In the .env file in the root of the project folder — next to the portal content folder. That is a convenient place for the portal management key, the key to your Xedant Agent and everything else you would rather not spell out in compose.yml. It never gets into git: it usually holds keys. The file is read at startup and re-reads on the fly: edits apply within a second, without a restart. Settings that are read once at startup (the database, the agent address and key, the license, the brand) are picked up after the container restarts. Details are on the Installation page.
Can part of the portal be opened to the outside?
Yes. A page with “public” access opens for everyone at /p/, and the public site’s menu is built from the published pages — with the order and depth you set. Drafts and internal pages look exactly like non-existent ones from the outside: nobody will even guess they exist. Details are in the Page Access and Public Site sections.
Are dynamic block scripts safe?
The scripts are as much a part of the content as the page text, and they are written by the managing agent you trust. They run right on the server, in a separate Python environment: without launching a system shell, with a time limit (usually up to a minute for filling a page and up to two minutes for an action) and at most four at a time. There is no separate isolated “sandbox”: a script runs with the application’s rights, so trust in whoever edits the files matters here just as with any other code.
Will the portal be slow?
The pages themselves are read from files, so they open fast. Script results can be kept for a while: the period is set in the block’s settings, and then a repeat view takes the ready result without pulling your systems again. By default the script runs on every open — handy for fresh numbers — and for heavy calculations it is enough to set a storage period of a few minutes. Details are in the Dynamic Python Blocks and Charts sections.
How much does it cost and what does the license give?
The personal license is
How do I install the portal on my server?
As one container through Docker Compose: by default the application listens on port 3992, and the data stays with you in the permanent volume. A separate database and Python are not needed — they are inside the image. The step-by-step walkthrough with all the settings is on the Installation page.