Sign InCreate Account
Licensed self-trading engine · client-owned infrastructure

Your engine runs in your AWS.
Your broker account stays yours.

RAYOK deploys a protected self-trading engine to an approved client server and connects it to the client’s own Angel One account. The central platform manages onboarding, license binding, approved versions, readiness evidence and support controls—it does not hold client capital or act as the client’s broker.

Create Account →Understand the Product →View Factsheet →
Account registration is openMumbai · ap-south-1t3.micro client serverAngel One executionTrade Ready required
RAYOK product architecture showing signed contract delivery, client-owned AWS engine and Angel One execution
01
Licensed per bindingApproved client account, server fingerprint, broker identity and engine version must match.
02
Product-controlled strategyClients approve quantity, capital method and operating mode; proprietary strategy rules are not client-editable.
03
Broker proof is finalOrders, fills, cancellations and flat status require broker evidence—not only a request response.
04
Fail closedMissing, stale, mismatched or revoked proof produces NO_TRADE until the required evidence is restored.
Real product architecture

Three authorities, with clear boundaries.

RAYOK separates market-data preparation, client execution and central platform control so that no single public-facing portal is treated as the source of every truth.

M

RAYOK Master

Uses the approved market-data authority to prepare the daily signed trading contract for the client engine.

  • Owner-side market-data and reference authority
  • Signed contract delivery to approved clients
  • No direct authority to place orders in a client broker account
C

Client-owned AWS server

Runs the protected licensed engine and keeps the client runtime state, execution logic and broker evidence.

  • Mumbai region, hard-locked client server profile
  • Protected release—not editable owner source
  • One control session; additional approved sessions are monitor-only
A

Angel One account

Remains the execution authority for orders, fills, positions and final broker proof.

  • Client-owned broker account and capital
  • Client permissions and API access remain the client’s responsibility
  • Manual broker access must remain available for emergencies
Central platform boundary:

The RAYOK portal handles registration, AWS lifecycle, licenses, approved releases, readiness, monitoring and audit evidence. Central monitoring is not authority to place client trades.

Ownership and responsibility

What the client controls, what RAYOK provides, and what RAYOK is not.

Client owns and controls

  • AWS account, server costs and cloud permissions
  • Angel One account, capital and broker permissions
  • Approved quantity, capital method and operating mode
  • Broker credentials and emergency broker access
  • Monitoring, legal compliance and manual intervention decisions

RAYOK provides

  • Protected licensed client engine
  • Account, server and broker onboarding lifecycle
  • License binding and approved-version enforcement
  • Signed daily contract delivery and readiness gates
  • Heartbeat, evidence, audit and controlled support workflows

RAYOK is not

  • Not an investment adviser or personalised recommendation service
  • Not a pooled fund, custody service or capital manager
  • Not a public signal-copying or central order-routing service
  • Not a guarantee of profit, uptime, fills or limited loss
  • Not permission to trade before Trade Ready is confirmed
Client lifecycle

Account creation is immediate. Trading permission is not.

Registration opens the portal. Every infrastructure, identity, broker and safety requirement must still pass before the engine can report Trade Ready.

1
Account + legal

Create the account after accepting the current Terms, Risk, Privacy and Licensed Engine documents.

2
Email verification

Verify email before broker credentials or other sensitive setup can be delivered.

3
AWS + server

Connect AWS, create the Mumbai t3.micro server and complete SSM-managed server setup.

4
License + IP

Bind the approved account, server fingerprint, broker identity and engine version; complete IP readiness.

5
Broker + controls

Complete Angel setup and verification, quantity approval, Telegram verification and operating mode.

6
Trade Ready

Operate only when every required gate passes. Missing or stale proof keeps the engine blocked.

AWS Access→Create Server→Server Setup→License→IP Whitelist→Broker Setup→Broker Verify→Quantity→Telegram→Mode→Trade Ready
Operational safety

Designed around evidence, not optimistic status.

✓
Exact license bindingAccount, server, broker-client identity and approved version must agree.
↻
Broker reconciliationOrder, tradebook and position evidence are used to confirm the actual broker state.
!
Manual-required statesThe client must remain able to monitor alerts and intervene through the broker when required.
⌁
Controlled support accessSupport access is client-approved, time-limited, role-controlled and audit logged.
!

Trading and technology risk

Derivatives trading can cause rapid and substantial loss. Broker APIs, market data, cloud systems, internet connectivity and third-party services may fail or change. Past factsheet records do not predict future results.

Next step

Review the product before connecting infrastructure.

Read the exact lifecycle and responsibility boundaries, then create an account. An optional enquiry is available for setup or product questions; it is not required for registration.

Read Documentation →Create Account →Optional Enquiry