Skip to main content

​
Features

This page is the product view of what Fased supports today. Use it when you want the major capabilities without digging through lower-level implementation details.

​
At a glance

Gateway and control

Browser-first control surface, CLI, runtime policy, sessions, and logs in one self-hosted stack.

Channels

One runtime can serve many messaging surfaces at once instead of splitting identity across isolated bots.

Wallet, Fased Network, and SAT

Wallet policy, SAT mining, Fased Network identity, and bond controls are optional operator modules in the same runtime.

Offers and operator workflows

Local offers, public discovery, and reviewed operator readiness live in the control surface.

Nodes and devices

Mobile and local-device nodes extend the runtime to cameras, audio, screens, and Canvas-style surfaces.

Automation and plugins

Skills, plugins, hooks, scheduled tasks, and sandboxed tools let the runtime grow into operator-specific workflows.

​
Major features available now

​
1. Self-hosted gateway runtime

Fased gives you one runtime that you control on your own machine or server. Current core surfaces:
  • Dashboard, Chat, Agents, Logs, Usage, and Advanced operator surfaces
  • CLI for onboarding, status, channels, wallets, Fased Network, and ops work
  • session management and chat history
  • routing, logs, runtime health, and restart-safe service operation
  • local versus hosting profiles for different operator postures

​
2. Multi-channel messaging and remote access

Fased can expose one runtime across many communication surfaces. Current channel and messaging capabilities include:
  • WhatsApp
  • Telegram
  • Discord
  • IRC
  • Mattermost
  • iMessage / BlueBubbles
  • Slack
  • Signal
  • Matrix
  • Nextcloud Talk
  • Microsoft Teams
  • Feishu
  • Google Chat
  • Synology Chat
  • Line
  • Nostr
  • Tlon
  • Twitch
  • Zalo
  • Zalo Personal
  • group chat and mention-based activation
  • images, audio, and document handling
  • long-response streaming and chunking
The important product point is not any one connector. It is that the same self-hosted runtime can serve many channels at once.

​
3. Agent runtime and routing

Fased is not just a message relay. It is an agent runtime with operator controls. Current agent capabilities include:
  • multi-agent routing
  • isolated sessions by workspace, sender, or agent role
  • memory and session compaction
  • tool use and plugin tool registration
  • embedded Fased agent runtime over the gateway RPC path
  • provider auth and subscription/OAuth paths where supported
  • sandbox and tool-policy controls

​
4. Wallet runtime

The wallet layer is now a real product surface, not an afterthought. Current wallet features include:
  • wallet inventory and role visibility
  • send flows and recent wallet activity
  • signer health checks
  • shared wallet policy and spend limits
  • Agent wallet visibility
  • mining wallet visibility
  • bond Vault visibility
The wallet page is the inventory and policy surface. It is not the place for mining control or bond lifecycle actions.

​
5. SAT mining

SAT mining is a first-class capability in the runtime. Current mining features include:
  • SAT mining page and controls
  • capital, commit, and cycle visibility
  • singleton Mining wallet assignment
  • cycle history and operator activity
  • restart-aware runtime support for continued operator use
Mining is the SAT issuance and participation layer. It is not the same thing as payments or bond.

​
6. Fased Network identity and public participation

Fased Network is the network participation layer on top of a healthy runtime. Current Fased Network features include:
  • handle and token state
  • trust and hosted status visibility
  • hosted-route health awareness
  • public participation readiness checks
  • self-hosted runtime identity tied to the same operator stack
Fased Network is how the runtime becomes a public network participant. It is not a replacement for local runtime control.

​
7. Bonded operator path

Bond is the SAT-backed trust and eligibility layer for operators. Current bonded operator features include:
  • bond Vault selection
  • bond open / top-up / unlock / withdraw lifecycle
  • proof of bond Vault control
  • derived operator scopes
  • bonded lane readiness in Fased Network UI
Current first-layer bonded capabilities include:
  • publishing public offers
  • clearer payment setup visibility
  • basic directory priority
  • basic routing priority

​
8. Offers and marketplace

Fased now includes the operator surfaces for local offers and public discovery. Current offer/operator surfaces include:
  • local offer publishing and management
  • public marketplace discovery
  • selected-offer execution surface
  • payment setup and review flow separation
  • bonded public visibility model
Important boundary:
  • local offers can exist without public bonded visibility
  • marketplace discovery is separate from any payment provider
  • bond does not replace the payment layer

​
9. Operator status and evidence

Operator accounting and evidence surfaces exist today, but later fee-related surfaces remain controlled rollout items. Current operator status features include:
  • operator status surface
  • read-only and gated readiness states
  • accounting / reserve / reconciliation evidence surfaces
  • read-only operator reporting
  • fee-related reporting groundwork
What is true right now:
  • bond is live
  • bonded operator lanes are live
  • operator status and evidence surfaces exist
  • full live collection and service-fee paths remain controlled rollout items

​
10. Plugins, skills, and automation

Fased supports operator-specific extension and automation paths. Current extension features include:
  • plugin manifests and plugin agent tools
  • community and extension package support
  • crypto plugin surfaces
  • hooks
  • scheduled tasks
  • webhook and polling flows
  • Gmail Pub/Sub automation path
  • browser automation and tool workflows

​
11. Nodes and device surfaces

The runtime can extend into paired device and node surfaces. Current node features include:
  • iOS node
  • Android node
  • Canvas-style mobile surfaces
  • camera, audio, and media understanding paths
  • local device pairing and remote-node workflows

​
Current feature map by product area

If you want the shortest product summary, read it like this:
  • Gateway: self-hosted runtime, CLI, browser UI, health, sessions, logs
  • Channels: remote chat surfaces across many messaging platforms
  • Agent runtime: routing, tools, memory, sessions, policy
  • Wallet: inventory, signer health, send flows, wallet-role visibility
  • Mining: SAT issuance and mining operations
  • Fased Network: public identity, trust, hosted route, network participation
  • Bond: SAT-backed operator eligibility and proof
  • Offers: local publishing and remote discovery
  • Operator status: evidence and controlled maturity path
  • Nodes: mobile and device-linked runtime surfaces
  • Plugins and automation: extension and workflow system

​
Roadmap, not current features

Do not treat roadmap items as live features. The next public roadmap lanes are:
  • bonded verified chat
  • stronger operator evidence and operator controls
  • reviewed market automation lanes
  • news and market-intelligence tools
See Roadmap for that next tranche.