Documentation

The product, clearly explained.

What RAYOK is, who controls what, how onboarding works and what must remain true before the engine can operate.

Product model

One protected engine binding for each approved server and broker account.

RAYOK is a licensed platform for onboarding, deployment, licensing, readiness, monitoring, evidence and support. Its protected client engine runs on the client’s approved AWS server and sends order requests only through the client’s own Angel One account. Creating a portal account does not activate trading.

RAYOK platformOnboarding, licenses, approved versions, readiness, monitoring and audit.
Client AWSProtected engine, runtime state and local broker evidence.
Angel OneExecution authority and broker proof for orders, fills, cancellations, positions and final flat status.
Onboarding

The single required order to Engine Ready.

01

Create Account → Verify Email → Sign InAccept current legal documents and verify the registered email.

02

Connect AWS → Create Server → Server ReadyConnect client-owned AWS, create the approved Mumbai t3.micro server and complete Agent/engine installation automatically.

03

Broker Setup & VerifyIP whitelist guidance remains inside Broker Setup. Successful verification activates Open Licence automatically.

04

Trading Quantity → TelegramApply the chosen quantity method and verify the official Telegram alert connection.

05

Engine ReadySetup is complete. Use Control Room, Open Engine and Reports. Server Power defaults to Auto, starts at 09:00 AM IST on market days, and stops only after trusted DAY_DONE acknowledgement; it may instead be set to Always On.

Responsibilities

Ownership stays clear.

Client

  • Owns AWS, broker account and capital
  • Approves quantity and operating mode
  • Maintains emergency broker access
  • Handles applicable legal and tax duties

RAYOK

  • Provides the licensed platform and protected client engine
  • Controls approved engine releases and license state
  • Calculates readiness and records operational evidence
  • Provides controlled, client-approved and audit-logged support

Broker

  • Receives order requests and proves orders, fills and cancellations
  • Proves positions and final flat status
  • Remains the execution authority
  • May fail, reject or delay requests
Operating rules

Fail closed, prove broker state, keep manual access.

Live operation requires current evidence.Missing, stale, mismatched, expired or revoked proof blocks operation.
A request is not completion.Broker evidence is required for final order, cancellation, position and flat status.
Manual intervention remains possible.The client must monitor alerts and retain direct broker access for emergency intervention.
No guaranteed outcome.RAYOK does not guarantee profit, uptime, fill price, order completion or limited loss.
Credentials and support

Secrets do not belong in ordinary messages.

Broker credentials are designed for encrypted one-time delivery to the client-owned server, with the central sensitive payload deleted after acknowledgement or expiry. Never send passwords, API secrets, MPINs, TOTP seeds, private keys or active broker tokens by ordinary email, chat or enquiry form.