Protected Server

Run any trading app without handing it your keys.

Protected Server is your own cloud server for trading apps, whether a person or an AI built them. It keeps them online around the clock, holds your exchange keys where no app can see them, and lets each app do only what you granted.

Runtime illustration showing Protected Server staying online 24/7 inside SignalPlus OS boundaries and connecting Gateway, Action, Audit, and Network.

Protected by SignalPlus OS

It is called Protected because every layer is.

Keys, permissions, execution, risk and audit are this server's rules, not an app's good manners, so they hold whoever wrote the app.

Keys Bound to the ServerExchange and broker keys never leave your server once written. Apps can only call authorized capabilities and never see the keys themselves.
Sandboxed ExecutionEvery app runs in a closed sandbox. File and network access are off by default, and the only way out is a SignalPlus OS-authorized channel.
App-to-App IsolationEvery app has its own storage and runtime space. Apps cannot see each other or read each other's data.
Built-in AuditEvery server ships with an audit view. Data requests and order actions can be replayed and reviewed over time.
Install Is AuthorizationInstalling an app means confirming its data and trading permissions one by one. Capabilities you did not grant simply do not exist.
Emergency StopPlatform risk directives reach the server directly, and a misbehaving app can be terminated immediately.
The real Protected Server desktop, showing the Tokyo Protected Server's online status, specs, and installed apps.
Your server desktop: apps live on this machine
The real built-in audit timeline, with order and query events recorded by app, exchange, and key.
Built-in audit: every action traceable by app, venue, and key

Screens are from the current product build, with demo-environment data.

Runtime Ops

Safe is half of it. An app also has to keep running.

Protected Server is more than compute for running apps. It includes the operations needed for long-running systems: alerts, patrols, root-cause analysis, changes, reviews, and cost views around apps, Gateway, runtime state, and resource usage.

Event Hub

Event hub.

Alerts, tickets, runtime logs, and system events flow into one operating view, so Protected Server does more than spot anomalies. It understands where they happened in the chain.

Runtime exceptionneeds review
System eventclassified
Low-risk alertauto closed
Proactive Patrol

Proactive patrol.

Protected Server can continuously connect configuration, routes, metrics, logs, and app status to identify potential risk and resource anomalies before they become alerts.

Config drift Gateway route App metrics Resource anomaly
RCA & Cost View

Root cause and cost visibility.

From app to Gateway, network, and underlying resources, Protected Server traces anomalies and costs back to specific business, product, and resource paths.

Root cause path App → Gateway → Network → Compute
App Health Gateway Health System Events Resource Events Audit Trail Cost View
Protected Server

Choose the Protected Server your apps run on.

This is not a SaaS plan. It is a cloud trading server billed by the day, carrying your apps, data connections, execution parameters, and audit state.

Basic

Where you start: market dashboards, alerts, and lightweight monitoring.

Solo

The everyday server for individual traders: strategies stay running, with market data, execution, and risk controls all on board.

Business

High-frequency data, multiple accounts, and small-team workloads.

Institution

Dedicated runtime environments and compliance options for institutional teams.

Every tier is billed daily and settled in credits. Pick a deployment region close to your primary markets when creating one. Exact specs and pricing for each tier will be announced in the product.

Always On

Made for apps that never sign off.

Trading apps, and the agents inside them, need compute that stays on, keeps its state and sits close to the market. Phones, laptops, local scripts and generic cloud servers were not built for that.

Personal Cloud Device

The Next Personal Device Is in the Cloud.

Phone, computer, and glasses are simply ways into Protected Server. The real runtime is in the cloud, and SignalPlus OS keeps it consistent: wherever you open it, you connect to the same runtime environment.

Personal cloud device visual showing a phone, computer, and smart glasses connected to the same cloud Protected Server.

The app lives in the cloud. Every screen is just a way in. Change devices without changing environments. Turn off the screen and the runtime keeps going.

Institutions & Teams

Institutional options, from dedicated IPs to private deployment.

The boundary design of Protected Server is institutional by default: data sovereignty, network identity, and audit responsibility stay on your side.

Dedicated Network Identity Pro tiers and above come with a dedicated IP, making exchange and broker API whitelisting straightforward.
Data Stays on Your Server Trading instructions, credentials, and audit details stay inside the server. The platform center keeps only the control-plane metadata it needs.
Private Deployment Protected Server can run in your own cloud or data center while joining the same SignalPlus OS ecosystem. An organization admin console is on the roadmap.
Get Started

Run your first app on a server that is yours.

Log in, set up a Protected Server, then install an app from the Marketplace or one you built in Workstation.