SaaS Engineering · Browser Extensions · Platform Development

Building Safentry: A Real-Time Trading Risk Awareness Platform

A Chrome extension and SaaS platform that checks position size, leverage, allocation and account exposure on supported trading platforms and shows contextual risk warnings before a trade is placed.

Industry
Trading software
Project type
Browser extension and SaaS platform
Attribution
Product Engineering
  • Chrome Extension
  • SaaS
  • Next.js
  • Integrations

Simplified system overview

01 / Overview

Project overview

Safentry combines a browser extension and a SaaS platform to provide contextual pre-trade risk information.

The product evaluates factors such as position size, leverage, allocation, account exposure and the user’s own configurable risk rules.

Product Engineering. Engineering of the Safentry product.

02 / Challenge

The challenge

Trading interfaces differ in:

  • Page structure
  • Order-entry behavior
  • How balances are presented
  • Asset denomination
  • Leverage controls
  • The availability of third-party data

Around the extension, the product also needed authentication, account settings, subscription management, communication between the extension and the web platform, cross-platform integration and ongoing compatibility maintenance.

03 / Solution

The solution

An integrated browser extension and SaaS platform. The extension reads the order being prepared on a supported platform, evaluates it against the user’s risk settings and shows a warning in context. The web platform handles accounts, settings, subscriptions and warning history on shared backend services.

04 / Capabilities

Key capabilities

Contextual risk warnings

Warnings appear within the trading workflow, at the point of decision.

Trading input detection

Order details are read from the trading platform’s own interface.

Position-size evaluation

Orders are checked against the user’s position-size limits.

Leverage and allocation checks

Leverage and allocation are compared with configured thresholds.

User-defined risk settings

Users set the rules that matter to their own trading.

Account management

One account for the extension and the web platform.

Subscription infrastructure

Plans and billing integrated into the product experience.

Risk-warning history

Past warnings are recorded for later review.

Supporting web dashboard

Settings, subscription and warning history in one place.

Platform-specific compatibility

Detection logic adapted to each supported platform’s interface.

Platform integrations

One product, several very different interfaces.

Integration work has covered the following platforms. Each structures its pages, balances and order entry differently, so detection is built per platform, and the checks available may differ between them.

  • MEXC
  • Binance
  • Hyperliquid
  • pump.fun

Support depends on each platform’s interface and can change when a platform updates it.

05 / Architecture

Technical architecture

How the parts connect. The animated example follows real stages of the system; every step is also described in text.

From the trading page to the platform
  1. Trading platformExternal service
  2. Chrome extensionManifest V3
  3. Order & balance detection
  4. Risk evaluationUser’s risk rules
  5. Contextual warning
  6. Account & settings sync
    Account services
  7. SaaS web platformNext.js
  8. User settings
    SubscriptionsStripe
  9. Backend services
  10. SupabasePostgreSQL
  • Data flow
  • External service
  • Processing
  • Outcome
  • Storage & queues
A conceptual view. Security-sensitive implementation details are omitted. Warnings inform the trader; the decision stays with them.

How it works

  1. Detect the order

    On a supported platform, the extension reads the order being prepared and the relevant balance information from the page.

  2. Evaluate the risk

    Position size, leverage, allocation and exposure are checked against the user’s own risk settings.

  3. Warn in context

    When a rule is exceeded, a warning appears inside the trading workflow. The decision stays with the trader.

  4. Sync the account

    Account services connect the extension to the web platform for sign-in, settings and warning history.

  5. Run the product

    The web platform manages settings and subscriptions on shared backend services and Supabase.

06 / Decisions

Engineering decisions

  1. Warnings inside the trading workflow

    Risk information is most useful at the moment of decision. Showing it beside the order, not in a separate dashboard, keeps it where the trader is looking without taking the decision away.

  2. Platform-specific interface handling

    Each platform structures order entry, balances and leverage controls differently. Platform-specific detection is kept separate, so a change on one platform does not affect the others.

  3. Unreliable or missing external data

    Third-party pages change, and data can be missing or delayed. Detection treats unavailable inputs as a normal case to handle rather than assuming every value is present.

  4. Extension behavior separate from backend services

    The extension focuses on detection and display; accounts, settings, subscriptions and history live in backend services. Each can be changed and released on its own schedule.

  5. Authentication and subscriptions as one experience

    Sign-in and subscription state are shared between the extension and the web platform, so users manage one account across both.

  6. Ongoing browser extension compatibility

    Manifest V3 requirements and changing trading interfaces make compatibility continuous work. Isolated platform logic and managed releases keep updates contained.

07 / Stack

Technologies

  • Chrome Extension Manifest V3
  • JavaScript / TypeScript
  • React
  • Next.js
  • Supabase
  • PostgreSQL
  • Vercel
  • Stripe
  • Payment integrations

08 / Outcomes

Business outcomes

Safentry provides risk information. It does not prevent losses, guarantee outcomes or improve trading results, and no performance claims are made.

  • A working extension that brings risk information into supported trading interfaces.
  • Configurable rules for position size, leverage and allocation.
  • Accounts, settings and subscriptions managed through a web platform.
  • A history of past warnings for review.
  • An architecture that contains platform-specific change.

09 / Takeaways

What this demonstrates

  • End-to-end SaaS product engineering
  • Browser extension development against changing third-party interfaces
  • Authentication and subscriptions across an extension and a web platform
  • Product decisions that inform users without taking control from them

Discuss a similar project

Have a similar engineering challenge?

Tell us about the workflow, integration, or technical problem you’re trying to solve.