FAQ

Need some help?

Don't worry we got you, have a read of our frequently asked questions below:

Does the platform comply with security and regulatory requirements?

The platform ensures security and regulatory compliance through robust encryption, access control, and infrastructure protections. Data stored in AWS RDS is encrypted using AES-256, and critical fields are further secured with custom encryption keys. A role-based access model allows precise permission management, ensuring users have access only to the functions necessary for their responsibilities. Authorization and authentication are handled with IAM policies and secure protocols like TLS/HTTPS. Hosting on AWS provides world-class physical and network security, while all data transmissions are encrypted to maintain confidentiality. Additionally, the platform’s FIX API for order transmission meets financial industry standards, guaranteeing secure and reliable trade execution.

Is the system scalable?

Yes, the platform is designed for efficient scalability across multiple levels. Services are containerized and managed by Kubernetes (EKS), enabling automatic scaling based on workload demands, with high availability and failover mechanisms ensuring stability during node failures. It also supports multi-region deployment in AWS, reducing latency, enhancing availability, and meeting local regulatory requirements. Additionally, the platform is built to adapt to various legal frameworks, enabling seamless multi-jurisdictional support.

What are the platform’s technical specifications and reliability metrics?

Backups: AWS RDS is configured with an automated backup system and predefined retention periods, ensuring data recovery in case of incidents.

‍Failover and Replication: Databases are deployed in Multi-AZ mode, enabling seamless failover to another availability zone in the event of a failure without service interruption.

‍Monitoring and Alerting: AWS services like CloudWatch are used for continuous system monitoring and timely response to potential issues.

How does integration with external systems work?

Reluna integrates with banks and brokers using the following methods:

‍Receiving transaction reports and current positions:

‍Email: Reports are sent to a designated mailbox, from which they are retrieved and processed by the system.
‍SFTP: Reports are uploaded by the bank or broker to an SFTP server (either hosted by the bank or Reluna) and then processed.
‍Custom API: Some banks provide their own APIs for report retrieval.

‍Placing orders:

‍FIX API is used for sending trade orders to external executors.If a required integration is unavailable, implementing a new one typically takes between 1 and 4 weeks.

Is the platform a trading marketplace, and how are orders created, sent (API, manual, etc.), and executed? What order types (market, limit, etc.) are supported, and are there any restrictions?

Reluna is not a trading marketplace. Instead, it provides tools for creating and managing trade orders, which are transmitted via FIX API to external executors, such as banks or brokers, for execution.

Users create orders by selecting the asset, specifying the order type (e.g., market or limit), and defining any applicable limits. The system validates orders to ensure sufficient funds or assets are available and may apply additional checks based on platform settings. If FIX API integration with a broker or bank is available, orders are sent directly; otherwise, they are forwarded to a trader for manual handling. Execution feedback is automatically updated in the system for API-based orders or entered manually for others.

The platform supports market and limit BUY/SELL orders, with restrictions such as the inability to trade on margin (unless enabled) or limits on asset percentages or criteria set by the system.

Ready to transform your investment experience?

Start a free trial or schedule a personalized demo to see how Reluna can help you grow

Try Reluna for free Request a Demo