Platforms
Fased core runs through the Gateway. Node is the recommended runtime. The normal setup path is: Companion apps exist for macOS and mobile nodes. Windows and Linux companion apps are planned, but the Gateway is fully supported today. On Windows, the practical path is WSL2.Current UI model
- The Gateway serves the browser Control UI at
http://localhost:18789. - Normal setup is Agent-first: open Agents, select an Agent, then use its Models, Channels, Skills, Tools, Memory, Services, and Tasks tabs.
- Dashboard is the customizable overview board.
- Chat is the normal browser chat surface for the selected Agent/session.
- Advanced contains raw Config, Debug, and Nodes operator surfaces. Mobile and desktop companion devices appear under Advanced → Nodes.
Choose your OS
| Platform | Best current path |
|---|---|
| macOS | Gateway plus native menu bar companion. |
| Linux | Gateway host, local machine, VPS, or always-on node. |
| Windows | WSL2 for the Gateway. Native companion app is planned. |
| iOS | Mobile node connected to another Gateway. |
| Android | Mobile node connected to another Gateway. |
| Raspberry Pi | Low-power always-on Gateway host. |
VPS & hosting
- VPS hub: VPS hosting
- Raspberry Pi: Raspberry Pi
- Fly.io: Fly.io
- Hetzner (Docker): Hetzner
- GCP (Compute Engine): GCP
- DigitalOcean: DigitalOcean
- Oracle Cloud: Oracle
Common links
- Install guide: Getting Started
- Gateway runbook: Gateway
- Gateway configuration: Configuration
- Service status:
fased gateway status
Gateway service install (CLI)
Use one of these (all supported):- Wizard (recommended):
fased onboard --install-daemon - Direct:
fased gateway install - Configure flow:
fased configure→ select Gateway service - Repair/migrate:
fased doctor(offers to install or fix the service)
- macOS: LaunchAgent (
ai.fased.gatewayorai.fased.<profile>; legacycom.fased.*) - Linux/WSL2: systemd user service (
fased-gateway[-<profile>].service)