Platform Reliability

Alphio's platform is built for continuous availability, with maintenance windows, graceful degradation, and store-review safe-modes.

---

1. App Startup check

Every time the Alphio mobile app launches, it calls /v1/dashboard/app/startup to fetch:

• Force-update flag — whether the current native version must update before continuing.
• Remote config — feature flags, regional toggles, experiment buckets.
• Maintenance banner — any active maintenance notice.
• Review-mode flag — whether the build is currently in store-review mode (see section 4).

This single call is the source of truth for app-level gating decisions made before you reach the home screen.

---

2. Force-update

If a native version is below the minimum supported, the app shows a blocking modal on launch:

• The modal cannot be dismissed.
• The only action is "Update now" (deeplinks to the App Store / Play Store).
• Force-updates are used sparingly — typically for security fixes, breaking backend contracts, or store-required compliance changes.

Web versions update silently on next page load and do not require this flow.

---

3. Maintenance windows

For scheduled backend maintenance:

• A banner appears across the app (web and mobile) ahead of the window.
• During the window, affected surfaces may switch to read-only mode — you can browse research, watchlists, and history, but trade execution may be paused.
• Notifications continue to deliver where possible.
• The banner is removed automatically once the window ends.

Emergency maintenance follows the same UI path but with shorter notice.

---

4. App Store review mode

When a new native build is in Apple / Google review, certain sensitive content is hidden by a server-side flag from /v1/dashboard/app-review-config:

• Restricted-jurisdiction features may be hidden.
• On-chain and prediction-market surfaces may render in a reduced form.
• This affects only the build under review — production builds for end users are not changed.

Once a build is approved and released, the review mode flag is cleared and the full surface returns.

---

5. Deeplink attribution

When you install Alphio from a campaign link, the app performs deferred deeplink matching on first launch:

• Pre-install: the campaign click is fingerprinted by the install attribution provider.
• Post-install: on first launch, the app exchanges that fingerprint for the original deeplink target (e.g. a specific Market Brief, referral code, or onboarding flow).
• You land directly on the intended destination instead of the generic home screen.

This makes referral and campaign experiences continuous across the install boundary.

---

6. Telemetry & uptime SLO

Alphio instruments backend services, app startup, and trade rails with telemetry to detect regressions quickly.

warning

The exact uptime SLO target and the public status page URL are being finalized. We publish incident updates through a status page once an incident is confirmed — confirm the URL with the product team before linking from external channels.

---

7. Reporting outages

If you suspect an outage:

• Check the in-app banner — most known issues are surfaced immediately on the home screen.
• Use the feedback channel in Settings → Help & Feedback to report what you're seeing.
• Email support for account-impacting incidents (trade not placed, balance mismatch). Include account email, approximate time, and screenshots if available.

For step-by-step support contact paths, see the Support section of the docs.