01 / SOURCES
Manage every upstream
Browse the source catalog, configure budgets and credentials, run fetches, probe failures, and verify stored records.
REPOSITORY 02 / FORESIGNAL-ADMIN
The control plane for
everything behind the scenes.
Connect, configure, test, tune, secure, and monitor your intelligence engine from one dedicated native application. No custom web backend. No duplicate business logic.
Linux · macOS · Windows iOS · Android companion Scoped, secure connection
FORESIGNAL ADMIN / CONTROL PLANE CONFIGURE · VERIFY
One app for the operational life of a Foresignal instance
These are the supplied ForeSignal Admin interface designs, used here as a product showcase.
THE OPERATOR WORKFLOW
See state. Change state.
Prove it worked.
Configuration is only useful when you can verify the result. Admin is designed around observable, testable operations.
02 / GOVERN
Keep collection under control
See network usage and request budgets, adjust concurrency, and keep upstream requests paced.
03 / INTELLIGENCE
Choose how the engine reasons
Configure model providers and roles, analysis cycles, correlation recipes, and evidence vetting.
04 / EXTEND
Integrate specialized analyzers
Configure EDP add-ins, forecasters, and external intelligence inputs without embedding them in the core.
BUILT TO OPERATE, NOT TO VISUALIZE
Not another dashboard.
An actual control plane.
The engine owns collection, history, rules, analysis, and forecasting. Admin uses its published API to configure those functions and confirm their outcomes. It is intentionally separate from map and globe exploration.
First-run connection Validated configuration Operational diagnostics Notifications & health
foresignal-adminFlutter · native operator app
HTTPS / REST / SSE
foresignalSource of operational truth
No BFF. No separate admin server. No custom intelligence computations in the UI.
PAIR THE TWO CORE REPOS
Operate intelligence on your terms.
One backend. One purpose-built control plane. Nothing else required.