Skip to content

APEX UR — apex-ur.projecteidos.com

Vanity URL for the APEX workspace-builder login on the same paid ADB (E5) that hosts Parallax. Engineers and DBAs use this URL to access the APEX builder where the Parallax application is developed and where pre-prod work will live.

Field Value
Vanity URL https://apex-ur.projecteidos.com
Direct URL https://g8ee0cce1dad263-urprod.adb.uk-london-1.oraclecloudapps.com/ords/r/apex/workspace-sign-in/
Backend ADB E5 (UR-Prod, paid) — same as Parallax
Tenancy / compartment EIDOSDev1 / UR
Audience engineering / DBAs (Vishnu, Bradley)
Criticality shares Parallax's blast radius (same DB)
Maturity inherits Parallax's posture
Owner Vishnu Kant
Last reviewed 2026-05-06

1. At a glance

apex-ur.projecteidos.com is not a separate application — it is a friendly vanity URL for the Oracle APEX workspace-builder login on the UR-Prod ADB. From here, engineers sign into APEX, edit the Parallax application, and (once provisioned) will manage the pre-prod workspace too. Caddy on E1 routes the URL to the ADB's APEX builder endpoint; the same endpoint is also reachable directly at the Oracle URL above.

The vanity URL exists so we don't have to pay for the higher ADB tier that would let us assign custom domains inside ORDS itself.

2. Business purpose

  • Developer / DBA access to the APEX workspace where Parallax lives.
  • Future home of the pre-prod workspace (separate APEX workspace, separate schema, same ADB).
  • Allows Bradley and Vishnu to administer schemas, run PL/SQL, manage workspace users.

3. Audience

Engineering / DBAs only — should not be customer-facing.

4. Hosting & cloud infrastructure

Credentials in Vault

Same ur/ mount as Parallax: https://vault.448.global/ui/vault/secrets/ur/kv/list

Secret type Vault location
APEX workspace admin (VKANT and others) ur/ mount — specific keys listed at the URL above
ADB ADMIN ur/ mount

5. Technology behind it

Oracle APEX builder + ORDS, served from UR-Prod ADB. Same as Parallax.

6. Data it handles

The APEX builder gives full access to all schemas in the UR-Prod ADB — i.e., everything Parallax stores. No additional data class beyond what Parallax has.

7. External dependencies

OCI EIDOSDev1 tenancy availability; Caddy on E1 (vanity URL only — direct URL still works if Caddy is down).

8. Authentication & access

  • Login mechanism: APEX workspace user accounts. Vishnu's username is VKANT.
  • Workspace admin holders: Vishnu, Bradley.
  • MFA: not enforced (KI-031) — same gap as Parallax end-user login.
  • Public exposure: the direct ORDS URL is publicly reachable; anyone who knows it can attempt to log in. (KI-011)

9. Maturity assessment

Inherits Parallax's maturity. Additional concern: developer-facing URLs are sometimes left more permissive than customer-facing ones. Today neither has IP allow-listing or rate-limiting beyond Caddy defaults.

10. Known risks & vulnerabilities

  • Shares all risks with Parallax (same ADB, same E1 Caddy SPOF for the vanity URL, same single region, same no-MFA gap).
  • Public APEX-builder URL exposure (KI-011) — the direct Oracle URL is brute-forceable. Caddy-side restrictions (when added) can be bypassed.
  • Workspace deletion authority — anyone with workspace admin access can delete the workspace; APEX exports must be in Git for recoverability (Parallax is, per Parallax doc §5).

11. Impact if it goes down

If E5 ADB is up but E1 Caddy is down → vanity URLs fail but the direct Oracle URL still works as a developer fallback.

If E5 ADB itself is down → Parallax is also down; this URL isn't independently meaningful.

12. Owner & on-call

Same as Parallax: Vishnu primary, Bradley backup.

13. References & links

  • Vanity URL: https://apex-ur.projecteidos.com
  • Direct URL: https://g8ee0cce1dad263-urprod.adb.uk-london-1.oraclecloudapps.com/ords/r/apex/workspace-sign-in/
  • Same ADB as: Parallax (01)
  • Server: E5 Paid ADB UR-Prod
  • Domain: see domains.md