Skip to main content
Back to selected work

Vestdrop

A safer operating system for automated DCA cycles.

A transaction-aware product for strategy execution, broker-order reconciliation, lifecycle recovery, backtesting and Monte Carlo analysis.

View live product
VESTDROP / DCA CYCLERUNNING
CURRENT CYCLE#084Reconciled
01Allocation02Order03Fill04Reconcile
BROKER SYNCSTATE VERIFIED
Ownership
Product architecture · trading workflow design · full-stack engineering
Platform
Next.js · Supabase · Alpaca
Domain
Automated equity workflows
Status
Production
01

Context and operational problem

An automated DCA workflow crosses two sources of truth: the application's strategy state and the broker's execution state. Network failures, partial fills or delayed updates can leave those systems disagreeing about what happened.

Vestdrop makes every transition visible, compares broker and application state, and gives the operator a controlled path to inspect, reconcile and recover a cycle before execution continues.

02

System architecture

CONTROLDCA configurationAllocation & rulesStrategy engineNext valid action
TRANSACTION LIFECYCLE01Allocate02Submit order03Confirm fill04Reconcile
VERIFICATIONAlpaca APIOrders & positionsRecovery serviceCompare · repair · resume
03

What was built

  • DCA strategy configuration
  • Explicit cycle and broker-order lifecycle
  • Position and order reconciliation
  • Backtesting engine
  • Monte Carlo analysis
  • Operational controls and recovery tooling
04

Engineering decisions

01

Lifecycle-first domain model

Cycles and orders preserve explicit states so partial progress and failure are inspectable instead of hidden behind a single status.

02

Reconcile before advancing

Recovery services compare broker and application state before the next transition can execute.

03

Test transaction boundaries

Unit and smoke tests focus on order creation, state transitions and recovery paths where operational risk concentrates.

05

Evidence and validation

Alpaca service integrationBroker connectivity isolated behind a dedicated boundaryAutomated security gateRelease checks protect sensitive execution pathsLifecycle reconciliation testsRecovery behavior exercised at transaction boundaries
06

What I learned

Automation is not reliable because the happy path runs unattended. It is reliable when every intermediate state can be inspected and recovered. Vestdrop shifted the design focus from placing orders to preserving consistency across the complete lifecycle.

Have a complex workflow to simplify?

Start a conversation