Trading automation

Polymarket Copy Trading

A self-hosted Polymarket copy-trading product built around single-tenant installs, paper mode by default, local dashboard controls, and risk guardrails before live trading gets a vote.

  • Polymarket-first scope with a local operator dashboard
  • Paper mode, live-mode guardrails, and risk controls in the core plan
  • Designed as an installable product, not a hosted signal circus

Infrastructure experiment

RecallLayer

RecallLayer is a vector retrieval sidecar for existing databases. Instead of trying to replace the system of record, it focuses on compressed indexing, hybrid retrieval, and candidate generation your application can rehydrate later.

  • Compressed vector indexing and hybrid mutable/sealed retrieval
  • Built for semantic search, RAG, and recommendation-style workloads
  • Positioned as a sidecar, not a full database replacement

Local-first collaboration

Ghostboard

Ghostboard is a local-first collaborative whiteboard meant to keep working offline, sync cleanly when peers appear, and stay understandable enough that contributors do not need an archaeologist to add a feature.

  • Offline-first editing with sync as a progressive layer
  • Designed around CRDT-style collaboration and clear state boundaries
  • Part useful app, part playground for replayable whiteboard UX

Early-stage app

GuitarTabs

GuitarTabs is an early guitar tab app idea in the Moose orbit. It is still mostly scaffolding and intent, but that counts: not every good product starts life fully armored and breathing fire.

  • Early concept stage with room to define the product shape
  • Useful placeholder in the portfolio for music-related experimentation
  • Still deliberately modest on promises while the work is young

FAQ

How the portfolio is structured

Is Moose Software Company just RecipeChef?

No. RecipeChef is the leading public product, but Moose is the parent company and the broader portfolio includes ingredient operations, trading automation, retrieval infrastructure, local-first tools, and early utility apps.

Why list early-stage projects publicly?

Because a portfolio should show the shape of the work, not just the most polished room in the house. Some products are already public, some are still in their workshop era.