Senti
Product Features
Automation, operated for you.
Runtime, orchestration, visibility, deployment, and execution controls in one layer — so terminal uptime and broker connectivity never become your operation. Senti sells infrastructure measured in Trade Accounts. Not algorithms, and not a trading outcome.
Infrastructure already operating at live-beta scale
These figures show infrastructure activity and historical availability. They do not describe investment performance, strategy quality, expected returns, or a contractual uptime commitment.
One constraint creates all the others
Trading automation rarely fails because a team cannot describe a strategy. The operational drag appears around it: machines that must stay online, account state spread across terminals, manual EA delivery, unclear stop procedures, and execution history reconstructed from screenshots.
Senti addresses those problems with product capabilities that can be used through the Senti product, a confirmed Whitelabel deployment, an API integration, or a managed on-premise engagement. The exact interface, permissions, data surface, and service commitment depend on the selected deployment.
One constraint creates all the others
MT5 is mature and Senti replaces none of it. The constraint is architectural: an EA runs only inside a Windows terminal that must stay on. Senti operates that terminal for you; each row below is one consequence.
Those five are the capabilities. Because the abstraction is separable from whose infrastructure runs underneath and whose product it arrives in, the same capabilities reach an end user through more than one route: the self-serve Senti product, a Whitelabel deployment, an API integration, Senti Inside on a partner's own infrastructure, or a managed on-premise engagement. Those are deployment models, covered after the capabilities below, and the exact interface, permissions, data surface, and service commitment depend on the one selected.
A managed 24/7 automation runtime
The pain: the EA is automated, the machine is not. Keeping it live means provisioning a Windows VPS, patching it, and checking the terminal is still up — for every Trade Account you add.
The feature
Senti runs the supported automation runtime around the clock
The user's laptop and local MT5 terminal do not need to stay open for the supported workflow to continue. Senti operates the runtime and supported broker connectivity within the agreed deployment boundary. The strategy owner continues to own the strategy, configuration, and trading decisions.
- Remove VPS provisioning and terminal babysitting from the normal workflow.
- Keep the supported automation running when the local laptop is closed.
- Add Trade Account capacity without recreating a local runtime for every account.
- Give engineering and trading teams a clear infrastructure owner and escalation boundary.
Managed runtime does not remove market, broker, connectivity, or strategy risk. Measured live-beta uptime is historical evidence, not a default contractual SLA. Contracted availability and response commitments are confirmed for the selected deployment.
One dashboard for supported self-serve operations
The pain: the operation is reachable from one computer. MT5 shows positions, orders, balance, and equity perfectly well, on the Windows machine running the terminal. That machine is where the operation becomes visible and where it can be changed. Away from it, understanding what is running means asking someone for a screenshot.
Fleet Control gives Senti product users one place to review live positions and open orders; balance, equity, currency, and account status; activity for each supported strategy deployment; and the Trade Account associated with that deployment.
Authorized users can deploy a supported strategy, adjust the allocation and risk controls that the strategy exposes, and pause or stop the deployment. Fleet Control reduces the need to reconstruct account state from MT5 terminals, screenshots, or support chats.
Fleet Control is the operating surface for the self-serve Senti product. A Whitelabel, API, or on-premise deployment may present a different surface, confirmed for that deployment.
Trade Account orchestration for supported MT5 brokers
The pain: every additional account adds another machine to keep alive. One MT5 terminal instance holds one login. Running automation on several accounts therefore means several terminal instances: more credentials, server details, installations, strategy assignments, and places to check. Capacity growth multiplies environments, not just accounts.
The feature
A consistent operating workflow across connected Trade Accounts
Senti connects supported MT5 Trade Accounts and brings them into a consistent operating workflow. Each connected Trade Account retains its own broker connection, strategy assignment, configuration, orders, and runtime context. Fleet Control lets self-serve users move between connected accounts without turning those accounts into one shared strategy state. B2B workspace, integration, and on-premise isolation boundaries are confirmed during technical evaluation for the selected deployment.
- Review multiple connected accounts from a defined operating surface.
- Keep configuration and execution context associated with the relevant Trade Account.
- Add capacity according to the selected plan or contract.
- Pay for infrastructure capacity measured in Trade Accounts, not for a package of algorithms.
Senti supports MT5 brokers and account types that meet the documented connectivity requirements, which is not the same as every broker. The exact account, workspace, API, or deployment boundary is described for each engagement rather than an undefined promise of full isolation.
Two supported entry paths to a deployable EA
The pain: you ship a file, but the customer has to build an environment. Writing the EA is the part MQL5 already handles well. What does not scale is what happens after: the customer needs a Windows machine, an MT5 installation, and often a VPS before the file does anything.
Upload EX5 lets a developer bring an existing compiled .ex5 file into the Create EA workflow. The standard path does not require handing Senti the strategy's source code.
Author with AI assists the creation and iteration of an EA from a strategy specification. The developer remains responsible for testing, validating, and approving the EA before it is deployed to a live customer workflow.
The outcome
Move from file delivery to a repeatable operating workflow
Once approved and made available through the confirmed product flow, the EA can use Senti's managed runtime, Trade Account connection, operating visibility, and supported controls.
- Use one supported path to bring an EA into the Senti infrastructure layer.
- Preserve ownership of EA logic, source code, licensing, and commercial terms.
- Reduce repeated VPS and local-terminal installation work for the supported customer journey.
- Start with one EA and a controlled cohort before expanding the operating scope.
Create EA is not a public EA marketplace, a substitute for developer testing, or a guarantee of strategy performance. Author with AI assists authoring and iteration; it does not validate trading logic or promise a profitable EA.
Timestamped activity from real execution
The pain: the history has no link. MT5 keeps a full order history, inside the desktop application, with no URL to send anyone. So verification travels as screenshots and messages, and it stays hard to confirm what ran, separate strategy behavior from infrastructure behavior, or give support a reliable starting point.
The feature
Replace anecdotes with reviewable activity
The Senti verification record presents timestamped order history and activity that ran on the linked Trade Account. A shareable view can show execution activity without exposing account credentials or withdrawal access. For B2B deployments, the reporting, reconciliation, export, retention, and sharing surface is confirmed for the selected Whitelabel, API, or on-premise scope.
- Review what orders ran and when.
- Give support and operations teams a factual activity record.
- Share execution evidence with the appropriate audience and permissions.
- Use recurring operational patterns as an input to service improvement.
Execution records show activity, not expected returns, strategy quality, regulatory compliance, or an independently audited performance result. They are not a profit forecast or a guarantee.
The five capabilities above are what Senti does. The sections below are the routes through which those same capabilities reach an end user. A buyer selects one of them rather than adding it to the others.
An own-brand product model on Senti infrastructure
The pain: a desktop terminal cannot carry your brand. Trading Groups, Trading Academies, and Strategy Developers may already have a brand, customers, education, and strategies, but MT5 is somebody else's Windows application. It cannot be skinned, embedded, or handed to customers as your product.
The feature
Your brand and offer on Senti's automation infrastructure
A Senti Whitelabel deployment applies an agreed customer-facing brand and product scope to Senti's automation infrastructure. The customer retains its brand, strategies, customer relationship, education, service offer, and direct broker relationship while Senti operates the confirmed infrastructure layer. The agreement and production review define the actual scope, including:
- Supported branding and domain treatment.
- Strategy availability and customer activation flow.
- Customer-facing monitoring and control fields.
- Administrator roles and support access.
- Workspace and data-separation boundaries.
- Reporting, billing, offboarding, and support responsibilities.
The Whitelabel model gives the organization a path to serve customers through an own-brand product while using Senti for the confirmed automation runtime, connectivity, and operational layer. It can reduce the amount of product and infrastructure work that the organization would otherwise need to own.
Brand controls, custom-domain setup, moderation, user management, reporting, workspace isolation, customer-facing controls, and self-service administration must be verified against the production deployment before they are presented as available features. Standard Whitelabel is not a source-code purchase or a promise of a native mobile application.
Senti execution infrastructure behind your product
The pain: a desktop binary cannot live inside your product. A fintech or trading product has its own users, interface, onboarding, and billing, and no way to embed a Windows desktop terminal into a web or mobile app.
The feature
Add trading automation without rebuilding the execution stack
The Senti API model lets the customer's product remain the user-facing experience while Senti operates the confirmed execution layer underneath. API engagements can cover account provisioning, strategy deployment, order submission, position and account queries, execution-event streams, webhooks, reconciliation inputs, and reporting exports within the agreed integration scope. The customer keeps its frontend, product flow, brand, billing relationship, and customer support. Senti owns the technical service boundary established in the integration agreement.
- Keep users inside the existing product experience.
- Use execution and account events as inputs to the customer's own interface.
- Define monitoring, failure handling, reconciliation, and escalation before production launch.
- Start with one provisioning-to-reporting journey before adding more accounts or product flows.
The exact endpoints, authentication model, permissions, rate limits, sandbox scope, broker coverage, data fields, retention, SLA, and production timeline are confirmed during technical evaluation. An API engagement does not transfer strategy responsibility or make Senti the customer's end-user support team.
The same abstraction, delivered through the provider
The pain: a hosting provider rents the machine, not the abstraction. A VPS provider selling MT5 instances to algo traders supplies the infrastructure layer competently. What it cannot supply is the layer above it: the customer still provisions the terminal, keeps it connected, deploys the EA, and checks on it through a remote desktop session.
- The Senti Inside agent is installed onto the MT5 terminals running on the provider's own instances.
- It reports terminal state, EA state, account state, activity, and health to a surface the provider's customers reach from a browser.
- The surface is delivered from the provider's admin system under the provider's brand.
- Supported control actions, their permission model, and their failure behavior are confirmed during technical scoping, not assumed to be a general remote command channel.
Senti Inside is the same abstraction layer reaching users through a different distribution channel, not a different architecture. Exactly two things change: the partner operates the infrastructure instead of Senti, and the end user works in the partner's admin system under the partner's brand. It is not a migration path onto Senti's infrastructure, and no rate, per-terminal price, revenue share, or setup fee is published.
How the product works
Link a supported MT5 Trade Account or confirm the account-provisioning boundary for the selected B2B deployment.
Deploy a supported strategy, upload a compiled EX5, use Author with AI, or integrate the agreed strategy workflow through API.
Use Senti-managed runtime or the contracted on-premise deployment boundary.
Review the fields provided by the selected operating surface and use its confirmed pause, stop, disconnect, or API controls.
Use execution activity and operational evidence to support verification, troubleshooting, and deliberate expansion.
The self-serve and B2B paths do not have the same onboarding timeline or feature surface. No universal activation-time claim applies across every deployment.
A clear line between your operation and Senti's
Funds remain at the user's broker. Senti provides trading automation infrastructure, not investment advice, discretionary account management, or guaranteed trading outcomes.
What people ask before the demo
Does Senti replace MT5? +
Is this not what MetaTrader VPS already does? +
MT5 has mobile apps and a Web Terminal, is that not the same thing? +
Do we have to give up the MT5 tooling we already use? +
Bring one workflow. Leave with a scope.
Trade Accounts, strategy path, operating pain, control requirements. We will map them to the smallest Senti scope that proves the fit.