We are a technology-driven company specializing in financial services infrastructure. Our platform enables fast, secure, and compliant operations across multiple markets and brands.
What is a Prop Firm?
A proprietary trading firm (prop firm) provides traders with funded accounts in exchange for a share of profits. Traders pass an evaluation challenge to prove their skill — if successful, they receive real capital to trade with.
We handle the technology, compliance, and operational infrastructure behind multiple prop trading brands. We don't trade ourselves — we power the platforms that traders use.
Our Business Model
Revenue comes primarily from challenge fees — traders pay to attempt the evaluation. A smaller portion comes from funded account profit splits. This means our success is directly tied to delivering a high-quality, fair, and reliable trading environment.
The Team's Role
Every team member — from Support to Engineering to Marketing — contributes to one core outcome: giving traders a platform they trust. Understanding this context makes every decision easier, from how we handle a support ticket to how we configure a new challenge.
From a team of three to a multi-brand operation — this is how we got here.
Q1 2025 — Founded
Founded with a single brand, Lumira, and a team of three. The goal was simple: build a prop firm that traders actually respect. No gimmicks, no unfair rules — just a clean challenge product and honest payouts.
Q3 2025 — Alpha Edge
Alpha Edge launched as our second brand, targeting a different segment of the market. Revenue doubled within three months. It validated the multi-brand model: one operational team, multiple market-facing identities.
Q1 2026 — Vertex Capital
Vertex Capital entered beta. The team grew to 10 employees across 4 departments. This milestone made clear that we needed proper internal systems — scattered Google Drive folders and ad-hoc processes weren't going to scale.
Q2 2026 — Internal OS
We launched omoya — this platform — as our central internal operating system. Every team process now runs through one hub: onboarding, knowledge, reporting, brands, and AI tooling. The foundation for the next phase of growth.
All active brands and entities in our group. Each brand operates independently toward its audience, but shares our infrastructure, compliance framework, and team.
Lumira
Our first brand. Positioned for serious retail traders who value reliability and transparency over flashy marketing. Largest trader base in the group.
Alpha Edge
Targets aggressive traders with higher-risk, higher-reward challenge structures. More active marketing presence. Revenue doubled within 3 months of launch.
Vertex Capital
Our newest brand, currently in beta. Premium positioning, higher account sizes, institutional-grade challenge rules. Full launch planned Q3 2026.
Vision
We envision a world where launching a trading brand is as simple as configuring a template.
Mission
We build the internal operating system that lets great teams focus on what matters: delivering value to traders worldwide.
Our Values
These three values are non-negotiable. They inform every product decision, every hire, and every interaction — internally and externally.
- Ownership — Act like a founder. If you see a problem, fix it. Don't wait to be asked.
- Speed — Move fast, iterate, ship. Perfect is the enemy of done. Bias for action.
- Transparency — Share context, flag blockers early, over-communicate. No surprises.
This isn't about rules — it's about mindset. The people who thrive here share a few common traits. Understanding them early makes everything else easier.
Take Ownership
Don't wait for a ticket, a meeting, or permission. If you see something that could be better — a broken process, a missing document, a confused colleague — own it. The best ideas here have come from people who just decided to fix things without being asked.
Move Fast
We ship imperfect things and improve them. A 70% solution shipped today beats a 100% solution shipped next month. If you're unsure whether something is ready, ship it and iterate. Speed builds momentum.
Communicate Clearly
In a remote-first, multi-brand environment, clarity is a superpower. Over-communicate status, flag blockers the moment you hit them, and write things down. If it's not documented, it doesn't exist.
Ask Questions Early
There are no stupid questions here. A question asked in day one is better than a mistake discovered in week three. Ask early, ask often — and share what you learn so others benefit too.
Our operating rhythm is designed for async-first work with structured sync touchpoints. Here's what a typical week looks like.
Daily Standup
Every workday at 9:30 AM CET. 15 minutes max. Three questions: what did you do yesterday, what are you doing today, any blockers? If you can't make it, post a written update in Discord before 10:00 AM.
Sprint Cycle
We work in 2-week sprints. Sprint planning happens on Monday morning — you'll commit to your deliverables for the sprint. Retro and review happens on the Friday of week two. All tasks are tracked in the project management tool; nothing lives only in someone's head.
Communication Tools
- Discord — internal team communication. Real-time questions, quick decisions, department channels.
- Slack — external communication with clients, partners, and contractors.
- omoya (this platform) — documentation, knowledge, reports, onboarding. The source of truth.
Video Tutorials
Step-by-step screen recordings for common internal processes live in the Resources section. Check there before asking how to do something — most things are already documented.
Overview
We are a fully remote team. There is no physical office requirement. You may work from anywhere, provided you meet the availability and communication standards below.
Availability
Core hours are 9:00–17:00 CET. You must be reachable on Discord during these hours on working days. Outside core hours, async communication is the norm — no expectation of immediate response.
Equipment
The company provides a laptop on day one. You are responsible for a stable internet connection (minimum 20 Mbps for video calls). If your setup is inadequate, raise it with your manager — we'll find a solution.
Overview
We encourage the use of AI tools to improve productivity and quality of work. This policy defines what is permitted, what requires approval, and what is off-limits.
Approved Uses
- Drafting and editing internal documents, emails, and reports
- Summarizing tickets, call transcripts, or large documents
- Writing or reviewing code (with human review before merging)
- Research and knowledge synthesis
- Using the omoya Ask AI feature for internal knowledge queries
Restrictions
Do not input client personal data, financial account details, or proprietary trading data into external AI tools (ChatGPT, Claude.ai, Gemini, etc.). Use only the internal AI via omoya for queries involving sensitive data.
Overview
All team members are required to handle personal and financial data in accordance with applicable data protection laws. Any suspected breach must be reported to your manager within 1 hour of discovery.
Data Handling Rules
- Never share client data via personal email or messaging apps
- Use only company-approved tools for storing or processing sensitive data
- Lock your screen when stepping away from your device
Breach Reporting
If you suspect a data breach — even a minor one — report it immediately. Early reporting enables us to contain the issue before it escalates.
Eligible Expenses
Software tools, home office equipment (up to €500/year), and work-related travel are reimbursable. All expenses require prior approval for amounts over €200.
Submission Process
Submit receipts via the Finance channel in Discord with the tag #expense. Include: amount, date, business purpose, and receipt photo. Reimbursement is processed monthly.
Non-Eligible
Personal meals, entertainment not related to a business meeting, personal software subscriptions, and hardware above the annual cap without prior written approval.
Respect & Inclusion
We treat every person — colleague, contractor, or client — with respect. Discrimination, harassment, or exclusionary behaviour has no place here. If you witness or experience it, report it immediately to a founder.
Conflicts of Interest
Disclose any financial interest in a competitor, client, or supplier. When in doubt, disclose — keeping it hidden is always the worse choice.
Confidentiality
Don't share unreleased product plans, financial information, or personnel details outside the company. This includes on social media, in communities, or in casual conversations.
Where we're headed, and when. This is a living document — updated at the start of each quarter.
Q2 2026 — Now
Full rollout of omoya: AI-powered knowledge base, automated onboarding flows, brand management, and reporting. All team processes running through one platform.
Q3 2026
White-Label Template. Package omoya as a purchasable template for other companies (50–500 employees). First external customers onboarded. Vertex Capital fully live.
Q4 2026
4th Brand + 20 Employees. Scale the team, launch another funded trading brand, and automate more operational tasks via AI agents. Target: 3× revenue vs Q2 2026.
Verified links for all company-owned digital properties. Do not share unverified or unofficial URLs externally.
Website & Legal
Social Media
Careers
Our mantra reflects how we approach every challenge — speed without sacrificing quality, iteration over perfection, and radical transparency with each other.
Our Values
These three values are how the mantra shows up in daily work. They're the lens we use when giving feedback, making trade-offs, and hiring.
How This Shows Up
Living the values is rarely dramatic. It's small, repeated choices: choosing a 60-minute write-up over a 6-hour investigation, flagging a slipping deadline the moment it's uncertain, or picking up a task nobody owns because it's adjacent to yours.
We run two chat platforms. They each have a clear, non-overlapping purpose — keeping them separate protects both internal candor and external trust.
Key Discord Channels
Your onboarding invite drops you into the core channels automatically. Department-specific channels are added as you meet your team.
- #general — company-wide chatter and announcements
- #announcements — read-only for milestones and rollouts
- #marketing — campaign planning and launches
- #support — tickets, escalations, coverage
- #dev — engineering coordination, deploys, incidents
Slack Usage Rules
Slack is not a place for internal debate. Think of it as email with a faster UI — everything you write there can and will be read by external parties.
- ✓ Partner communication
- ✓ Vendor coordination
- ✓ Client updates (select)
- ✕ Internal team discussion — use Discord
- ✕ Sensitive company info — use Discord or 1Password
The core tools every team member uses daily. Access is provisioned automatically during onboarding — if something's missing after day one, open a ticket in Help.
Access & Ownership
Each tool has a single owning department. Access questions, permissions issues, or onboarding gaps go to the owner.
- Google Workspace — IT Department · MFA required · access provisioned during onboarding
- 1Password — IT Department · invitation sent during onboarding · company-wide + department-specific vaults
Beyond the Core
Role-specific tools (design, analytics, dev platforms) are listed in the Tools directory with owners and access links. If you need something new, file the request with your manager.
The fixed meetings that shape our week. Check your calendar for team-specific calls on top of these.
Etiquette
- Camera on unless actively explained otherwise
- Mute by default when joining a call > 3 people
- Notes live in the meeting doc — linked in the calendar invite
- Can't make it? Drop a Discord note in the relevant channel before start time
The rhythms and rules that keep work predictable. These are the defaults — specific teams may layer their own cadence on top.
Operating Rhythm
Three processes anchor how work gets done across the company.
Quick Reference
The numbers and deadlines that come up most often.
- Standup time — Daily 9:30 CET
- Sprint length — 2 weeks
- Weekly report deadline — Friday 5 PM CET
- Expense cutoff — Last business day of each month
- Emergency contact — @founders on Discord
What we report, how often, and why. Submissions and history live in the Reports section — this page is the reference for what's required.
How to Submit
All reports are filed through the Reports section — the form pre-selects the correct type and guides you through the required fields.
Writing Good Reports
A good report is short and specific. Avoid status-theater — if a week was quiet, say so.
- Lead with what changed, not what's ongoing
- Quantify where you can — counts, dates, dollar amounts
- Flag blockers early, not in the summary of the week they killed
- Link to the artifact (doc, ticket, PR) instead of describing it
Overview
Google Workspace is our primary productivity suite — email, calendar, Drive, Docs, and Sheets. Every team member gets a company account during onboarding.
@company.com account. Personal Google accounts are not allowed for company work.How to access
Where is the password stored?
Your personal login is yours — do not share it. Service-account credentials and shared logins live in 1Password under the Google Workspace vault. Ask IT for access if you don't see the vault.
Who to ask
Reach out to the IT team in the #it-help Discord channel for account issues, access requests, or license changes.
Overview
Discord is where all internal team communication happens — text channels, voice rooms, and async threads. It replaces day-to-day email for everything team-internal.
How to use it
Where is the password stored?
Personal Discord accounts — manage the password yourself, ideally via 1Password. We do not share Discord logins.
Who to ask
Ops owns the Discord server. Reach out in #ops or DM the Ops lead for server-level questions (channels, roles, bots).
Overview
Slack is used exclusively for external communication — shared channels with clients, partners, vendors, and agencies.
How to access
Where is the password stored?
Personal account — store your password in 1Password. Enable 2FA via authenticator app.
Who to ask
Ops owns the workspace admin. Ask in #ops for channel requests, guest invites, or billing.
Overview
1Password is the single source of truth for every shared credential — service accounts, API keys, vendor logins, Wi-Fi passwords. Never store credentials anywhere else.
How to use it
Where is the password stored?
Your master password is the one you memorize. Everything else lives in 1Password itself. If you forget your master password, use your Emergency Kit to recover.
Who to ask
IT owns the 1Password account. Ask in #it-help for vault access, audits, or onboarding new team members.
Overview
Vercel hosts all frontend deployments. Every production push to main deploys automatically; pull requests get preview URLs.
How to access
Where is the password stored?
You sign in via Google SSO — there is no separate password. Personal access tokens live in 1Password under your personal vault.
Who to ask
Engineering owns Vercel. Ask in #engineering for new projects, domain changes, or deploy failures.
Overview
Figma is where all UI/UX design work happens — wireframes, mockups, prototypes, and the design system. Engineering pulls tokens and assets directly from Figma.
How to use it
Where is the password stored?
Google SSO — no separate password. Your account is tied to your @company.com email.
Who to ask
Design owns the Figma team. Ask in #design for access, plugin requests, or library changes.
This playbook covers the end-to-end process for configuring a new trading challenge — from initial setup through activation and monitoring. Follow each step in order to ensure consistency across all challenge types.
1. Pre-Configuration Checklist
Before opening the admin panel, verify the following are in place:
- Challenge type confirmed (Standard / Aggressive / Instant)
- Account size and step structure approved by Risk
- Drawdown rules and daily limits defined
- Profit split percentage locked by Finance
- Pricing set and confirmed by Leadership
2. Platform Setup
Log into the admin dashboard and navigate to Challenges → Create New. Fill in each field according to the approved spec sheet. Do not use default values — every parameter must be explicitly set.
Account Parameters
Set the starting balance, maximum daily loss, and overall drawdown limit. Double-check that the percentage values match the approved spec — a one-decimal error here will affect every account generated from this template.
Trading Rules
Configure allowed instruments, trading hours, and any news-trading restrictions. If the challenge includes weekend trading, ensure the risk engine is enabled for those sessions.
3. QA & Testing
Before going live, run the challenge through the staging environment with a test account. Verify that drawdown triggers correctly at the configured threshold and that the profit target locks the account when reached.
4. Go-Live & Monitoring
Activate the challenge during low-traffic hours (ideally Sunday evening UTC). Monitor the first 20 live accounts closely for the first 48 hours and report any anomalies to Risk immediately.
Follow this checklist for every new team member on their first day. IT should complete all steps before the employee's start time.
1. Accounts & Access
- Create Google Workspace account (
firstname.lastname@company.com) - Add to relevant Google Groups for their department
- Create 1Password account and share the team vault
- Invite to Discord (internal) and Slack (external comms)
- Set up MFA on all accounts before handing over credentials
2. Hardware
Issue a company laptop pre-imaged with the standard software bundle. Confirm the employee signs the hardware acceptance form before receiving the device.
3. Internal OS Access
Create their account in omoya with the correct role and department. They should receive the invitation email before Day 1.
Payout disputes must be resolved within 3 business days. This SOP ensures every case is handled consistently and documented for compliance purposes.
1. Intake
When a dispute ticket is received, immediately tag it payout-dispute in the support system and assign to a senior support agent. Notify Finance within 1 hour.
2. Investigation
Pull the full trade history for the account in question. Verify the payout amount against the calculation engine output. Check for any rule violations that may have affected the payout.
3. Resolution
If the dispute is valid, initiate a correction payout through Finance. If not valid, send the client a detailed explanation with the trade data attached. All resolutions must be logged in the audit trail.
This SOP defines the standard procedures for identifying, evaluating, and responding to trading risk events across all active challenges and funded accounts.
Daily Risk Review
The Risk team conducts a daily review at 08:00 UTC covering all accounts that hit 70% of their daily drawdown limit the previous session. Any accounts above threshold are flagged for intraday monitoring.
Breach Response
When an account breaches its drawdown limit, the system automatically restricts new orders. Risk is notified immediately and must acknowledge the alert within 15 minutes. A breach report must be filed by end of day.
Escalation Matrix
- Level 1 (single account): Risk Analyst handles independently
- Level 2 (>5 accounts same session): Risk Lead notified
- Level 3 (systemic event): Leadership + Finance alerted, trading may be paused
This guide covers the standard process for launching a marketing campaign — from brief to post-launch review. Applicable to all paid, organic, and partnership campaigns.
Brief & Approval
All campaigns start with a brief submitted at least 10 business days before launch. The brief must include target audience, budget, KPIs, creative assets, and compliance sign-off.
Creative Review
All creatives must pass a compliance check before going live. Avoid any claims about guaranteed returns or performance metrics that cannot be substantiated.
Launch & Monitoring
Campaigns go live Monday–Wednesday for maximum data collection time before weekend. Monitor daily spend and CTR for the first 72 hours. Any anomaly (>30% deviation from forecast) triggers an immediate review.
Pre-built prompts for use with Ask AI. Copy, paste into the AI chat, and replace the bracketed placeholders with the relevant data.
Ticket Summary
[Paste ticket text here]
Client Response Draft
Complaint: [paste complaint]
Our position: [paste internal notes]
Escalation Summary
[Paste ticket thread]
Step-by-step guide for launching a new brand under the company umbrella — from asset preparation through first-day go-live and post-launch review.
Pre-Launch Checklist
Placeholder — full content coming soon.
Asset Preparation
Placeholder — full content coming soon.
Go-Live
Placeholder — full content coming soon.
Post-Launch Review
Placeholder — full content coming soon.
Process for onboarding a new funded trader from purchase confirmation through first funded account activation.
Purchase Confirmation
Placeholder — full content coming soon.
Account Activation
Placeholder — full content coming soon.
First Login
Placeholder — full content coming soon.
Standard checklist for removing access and completing handover when a team member leaves the company.
Access Revocation
Placeholder — full content coming soon.
Handover
Placeholder — full content coming soon.
Exit Documentation
Placeholder — full content coming soon.
Defines the escalation path for client complaints that cannot be resolved at first-line support.
Escalation Triggers
Placeholder — full content coming soon.
Response SLA
Placeholder — full content coming soon.
Resolution Path
Placeholder — full content coming soon.
Prompts for analyzing risk data and generating risk summaries.
Drawdown Analysis
Placeholder — full content coming soon.
Position Sizing
Placeholder — full content coming soon.
Anomaly Detection
Placeholder — full content coming soon.
Convert rough notes into structured SOPs using these prompts.
From Notes to SOP
Placeholder — full content coming soon.
Formatting Rules
Placeholder — full content coming soon.
Review Checklist
Placeholder — full content coming soon.
