Skip to content
Rafael Aslanian
Who I build for

Software for medtech and clinical research teams

Somebody asks a question the system was never built to answer. Which version of the protocol was this collected under. Who changed that value. The answer is in an export, a shared drive and an email thread, and putting it back together falls to whoever knows the study best.

Where it usually goes wrong

  1. The record keeps the value and loses the history

    A record that updates in place keeps the current value and loses the one before it. Good Clinical Practice wants the old value, who changed it, when, and why. Adding that after the study opens means going back through backups to work out what the field used to say.

  2. Consent is easy to take and hard to withdraw

    The form captures it once and stores a yes. A withdrawal has to reach the analysis extract, the copy the statistician pulled for the interim look, and the partner who already has a dashboard. Capturing consent is a field in a database, and acting on its removal is a job that touches everything downstream.

  3. Every site connects in a different way

    One trust offers an HL7 v2 feed, another a FHIR endpoint that only answers from inside the network, and a third sends a spreadsheet somebody types into REDCap by hand. Each new site restarts the DSPT and DTAC conversation from the top, with a different information governance lead.

  4. Pseudonymised still points back at a person

    Strip the DICOM header and the patient's name can still be burnt into the pixels. The free-text box a clinician typed into carries more than every tick box on the form. The key linking a study ID to a patient has to live somewhere, and where it lives is the question.

Selected work

Selected projects

Products I built and open-source projects I maintain. Open a project to see the work for yourself.

  • 01
    2026

    Dr Flavia Pretti Aslanian

    Healthcare · Practice site

    A bilingual dermatology website for a practice in Harley Street and Wimbledon

    Dr Flavia's new dermatology landing page, with consultation booking and treatment navigation

    A new landing page guides patients to medical, aesthetic and surgical care. The practice edits its own content, and staff have a password-protected dictation tool in the same app.

    • Next.js
    • Sanity CMS
    • Tailwind v4
    • Radix
    • Motion
    • ISR
    • Railway
    • Cloudflare

    Design · Build · Deploy

    • 84 published English and Portuguese routes
    • 72 treatment pages with clinic-editable content
    • Custom before/after comparison UI
    • Internal clinician dictation tool
  • 02
    2026

    Continuum

    Web3 · DeFi protocol

    A Solana DeFi protocol for 24/7 synthetic exposure to real-world assets

    The Continuum page as it is published

    Deposit USDC, mint matched long and short tokens at NAV, sell the leg you don't want. A constant-product invariant keeps the pair redeemable back to the deposit.

    • Rust
    • Anchor
    • Solana
    • TypeScript
    • Pyth
    • Next.js
    • Bun
    • Railway

    Pre-mainnet. Devnet markets, audits pending.

    Protocol · Frontend · Infra

    • 5 Solana smart contracts in Rust
    • 8 synthetic markets on devnet
    • 4-state oracle risk machine
    • Volatility-scaled fee curve
  • 03
    2025 →

    Delta Xi

    E-commerce · Brand

    A mathematics apparel brand on a storefront I wrote from scratch

    Delta Xi's website hero, showing the front of a white T-shirt with a neural network diagram.

    I built the cart, checkout, product recommendations, affiliate programme and support desk, and run the infrastructure myself.

    • Next.js
    • React Server Components
    • Stripe
    • Auth.js
    • Tailwind
    • Umami
    • Chatwoot
    • Cloudflare

    Founder · Engineer · Operator

    • Custom checkout on Stripe + Klarna
    • Server-rendered recommendation engine
    • Self-hosted analytics and live chat
    • 50+ STEM explainers driving organic search
See 3 more projects
  • 04
    2026

    Dray

    AI tools · Product website

    A product website for keeping project context across AI agents

    The Dray page as it is published

    An editorial landing page introduces shared project context, shows illustrative agent workflows and explains setup and privacy ahead of beta.

      Beta coming soon. The public demos illustrate the workflow; they are not live agent connections.

      Design · Build

      • Interactive agent-linking illustration
      • Project-context walkthrough
      • Setup and privacy guidance
    • 05
      2026

      Tallylamp

      Open source · Browser infrastructure

      A browser for AI agents that you can watch and take over

      Tallylamp's public website, with an interactive demo of an agent handing browser control to a person.

      I built the browser service, dashboard, MCP server and public website. Agents use Chrome on your server while you watch the same browser live. Take control to sign in, then hand it back; saved profiles carry between sessions.

      • TypeScript
      • Next.js
      • Chrome
      • MCP
      • SQLite
      • Docker
      • Railway

      Public site at tallylamp.dev. The browser service and dashboard are self-hosted.

      Creator · Engineer · Maintainer

      • Live viewing and explicit human handoff
      • Separate agent permissions and reusable profiles
      • MIT licensed, with a Railway deploy template
    • 06
      2025 →

      CarClout

      SaaS · AI content engine

      A subscription app that turns a phone photo of a car into something worth posting

      The CarClout page as it is published

      Upload a photo, pick a template, get the edit back a moment later. Thirteen AI models sit behind a metered credit ledger, next to a layer editor, a post scheduler and a live chat room.

      • Next.js
      • SurrealDB
      • Auth.js
      • Stripe
      • fal.ai
      • Cloudflare R2
      • Stream.io
      • Railway

      Engineering · Infra · SEO

      • 724 generated landing pages, all live
      • 128 API routes behind one app
      • 13 AI models on a metered credit ledger
      • Instagram posting, scheduling and analytics
    Also on the books

    One runs on the client's own domain and one is internal to theirs, so there is nothing here of mine to show you.

    The rest

    Not everything is public. A fair amount of the work sits in private repositories I cannot hand you a link to. Ask, and I will walk you through it.

    Ask to see more
    Contact

    Have an idea? Tell me.

    A paragraph is plenty. I read every one myself and reply within one business day. If it isn't something I can do well, I will say so and point you somewhere better.

    Reply within one business day