Solutions
Download it yourself and run today — or bring in the FDE engineering team to install your first digital employees across your machines and intranet. Priced per project, handed over working.
Four steps to land agents on your real machines.
Four steps, not a flowchart — a contract, with each step's deliverable written in its anchor.
The four anchors are a checklist, not adjectives: the inventory matches your asset register, the server is loggable, roles have names, docs hand over to a new colleague.
Each delivery step has its own acceptor: you confirm the survey, you verify server login, you watch agents run real tasks, your new hires ask the questions. Every sign-off is yours.
We inventory machines, segments, and systems, then draw the boundary.
Your machines / segments / systems
Server up, machines enrolled, model channels ready.
Server + enroll + provider config
Agents tuned per role; RBAC and branding in; work begins.
Role tuning + RBAC + branding
Train, hand over docs, and you hold the keys.
Training + docs
When the four steps are done, every key to the boundary is yours — FDE delivers capability, not dependency. The server is yours, the keys are yours, and so is every enrolled machine.
From download to delivery, the bill and the boundary stay in your hands.
Download the client, one command for the server, one enroll for your first computer. Three steps, done the same day, with the docs matching every word.
A forward-deployed engineer lands with an agent squad: survey, deploy, land, hand over. When the four steps finish, your team runs role agents — and every key stays with you.
The tracks are not exclusive: most companies start self-hosted, land the first role, then decide whether FDE delivery is worth it.
On security review: everything FDE configures stays on your server, itemized in the handover report — what changed, what installed, what opened — line by line for your security team.
On timing: scope is confirmed in writing after the survey, and the cadence follows your change windows — every production operation lands in a slot you name.
Both tracks end in the same place: agent infrastructure you fully control, fully documented, verifiable at any time.
On the team: after handover your people run the system; the engineer does not become your standing dependency — that is what separates FDE from outsourcing, and why we quote per project rather than bill monthly.
Each role states three things: the work it does, the machines it runs on, the records it leaves. A role is an entry point, not a silo — all five share the same routing, approval and audit discipline.
The five roles below all run on the same self-hosted instance — only the deployment location and audit surface differ.
Every role follows the same first-month curve: week one, watch the agent run daily actions; week two, tune rules and permissions; weeks three and four, pull humans back to reviewing key decisions.
Statements, collection emails, and payment sheets — the agent works through them item by item under role rules.
Finance reconciliation has the most sensitive audit surface — every email is replayable, word for word, in a dispute.
Build failures, disk alerts, scheduled patrols — the agent keeps watch in the terminal.
Ops watch fails explicitly when a machine goes offline: alerts are never silently swallowed, and the human on watch always knows.
Inbound mail is triaged and drafted first; people review only the replies that matter.
Customer-support triage drafts but never sends; the final reply is always human-signed — the boundary sits on the send button.
Competitor pages and public sentiment — the agent patrols on a routine and summarizes.
Competitor monitoring patrols on a schedule with timestamped results, so any day's picture can be replayed.
Data scattered across systems — the agent compiles it into one daily report.
Report automation reads and writes only authorized directories, and every number traces back to its source system and file.
All five roles share the same routing, approval and audit discipline — add roles without adding new risk surface.
Delivery runs on an inquiry basis. When an FDE project ends, you hold these five things:
The list is checkable: walk it item by item at acceptance; a missing item means the delivery is not done.
01
A running server
02
Enrolled devices
03
Configured providers
04
Role agents
05
Documentation
Each deliverable has a documented acceptance: the server health check, the device-list export, a test model call, the role profiles, the doc index.
Nothing hidden beyond the list: no monthly service fee, no data egress fee, no premium unlock. Free to self-host means all of it, free.
On renewals: there are none. One delivery contract, closed when done — any further work is a fresh inquiry with no default terms.
After handover, adding machines, roles, or providers are all operations you complete yourself. The docs are in the repo and the process is in the docs — no follow-up meeting required.
To request a quote, write to mail@magicfrog.ai
One control plane orchestrates the server it lives on. That is a deliberate product boundary, not a tunable.
The boundary up front: you know exactly what the system looks like before signing anything.
Cloud computers are created only on that host; all state lands in one database file. No multi-host pool, no cross-machine scheduling.
Enrolled machines are outside that boundary — servers and desktops anywhere join the same control plane through their outbound daemon.
Run one host, land one role. Need more compute? Enroll more machines, or deploy another control plane per business line.
The other half of the boundary is data sovereignty: SQLite on your volume, keys in your environment, model calls through your egress. There is no such concept as our cloud.
Simpler inside the boundary means freer outside it: one server is one deployment, one backup, one upgrade path. Complexity goes into the product; simplicity stays with you.
One boundary dimension is easy to miss: upgrades. A single-file server upgrades by replacing one binary, the data directory untouched — rollback is swapping the file back.
The single-server boundary buys determinism: one server, one data file, one clear line of responsibility. Real machines are unlimited — scale follows your hardware.
These eight questions cover ninety percent of pre-delivery discussions. Ask the rest directly in the inquiry email.
Bring three facts to the inquiry: company size, the first role to land, and the constraints on internal-system access — scope comes in the first reply.
Anything not covered here goes straight into the inquiry email — answered by the engineers themselves.
If any answer above conflicts with your environment, your environment wins — verify first, adopt second. That is what self-hosting means.
Yes. Start self-hosted on a single machine and bring FDE in later to spread roles; after an FDE handover, daily scaling and maintenance are yours again.
Delivery happens on your machines and network: one target server, network reachability for enrollment, and the model keys you assign. The access scope is drawn in the survey step.
Discussed per inquiry. Three variables drive it: readiness of the target server and machines, the number of roles to land, and your approval flow for internal systems.
No. Data lives in the SQLite file on your server; model calls go to your chosen provider under your own keys. The FDE team leaves after handover — no standing channel.
Explicit failure is the product design: missing targets, offline machines, and missing permissions all fail immediately and stop in place. Daily handling is your team's; policy is yours to set.
Pick a process with clear rules and replayable actions — reconciliation or report compilation, for instance. Once the first role runs, the same discipline copies to the next line of business.
No. Delivery is a one-time project settled by quote. After that the software is free to self-host, and scaling and maintenance are your team's.
Calls to it fail explicitly — nothing is rerouted to another machine. When it comes back, it rejoins the available list; enrollment is unaffected.
From download to delivery, the bill and the boundary stay in your hands.
