Sites, bots, fixes. Shipped, not promised.

I'm Kurt Landman. I build websites, Polymarket trading tools and do smart-contract security review. Everything on this page is live, owned, or shipped for a real client.

polytraderbot.comsvaroglauncher.combtc09.orgfetchmux.comcantina 58/269

// services websites·bot dashboards·security review·remote fixes one owner, start to ship

01 // work

The work is the pitch.

Every case links to a live product, a shipped site, or a public trail. Open it and check.

PolyTraderBot dashboard

owned product [ live ]

PolyTraderBot

Self-hosted Polymarket trading automation. I own the product, the dashboard and the support surface, so status, controls and risk have to stay readable.

  • product ui
  • dashboard
  • live runtime
Open product ↗
PolyTortoise live product page

telegram bot [ live ]

PolyTortoise

Slow, risk-aware Polymarket automation in Telegram, built so the customer flow and the runtime state say the same thing.

  • product site
  • runtime state
  • customer flow
Open product ↗

public security work

Contract review with receipts.

DeFi review at the seams: accounting, AMMs, oracle paths, access boundaries and lifecycle edge cases. Findings are reproduced, evidenced and filed on public platforms. Only finalized work gets claimed.

02 // proof

Proof you can open.

Public pages beat invented case-study numbers. These links go to the real thing.

03 // services

What I actually do.

You deal with the person inspecting, building and shipping the work.

Websites

launch, rebuild or clean up

Small business sites, product pages and focused landing pages. Mobile layout, working forms, DNS, performance, SEO basics and launch verification.

Start a job ↘

Bots & dashboards

make runtime state legible

Operator dashboards, customer controls, state recovery and runtime validation for automation that cannot hide behind a pretty mock-up.

Start a job ↘

Security review

trace behavior, prove impact

Practical contract and application review with tight scope, exact state analysis and evidence you can reproduce.

Start a job ↘

Remote rescue

take over the ugly state

Broken deploys, DNS and email routing, account state, browser-only workflows and neglected integrations where the truth is scattered.

Start a job ↘

04 // process

How a job runs.

A URL, access, the failure state and the result you want is enough to begin.

  1. 01 send

    The ugly version

    What is broken, what you expected, what access exists and when it matters.

  2. 02 trace

    The real state

    I inspect the page, source, logs and account state before prescribing anything.

  3. 03 build

    The result

    The work happens against the real system with checkpoints where risk warrants them.

  4. 04 verify

    The handoff

    You get the working result, proof it is live and notes that make it durable.

05 // contact

Send the messy part.

A screenshot, URL, repo path, login state, error message and deadline is enough to start.

  • direct reply from Kurt
  • no sales sequence
  • private details stay private
[email protected]

You will hear from a person, not a funnel.

shipped workInk & Ivory Artistry
Full page capture of the shipped Ink and Ivory Artistry website
Ink and Ivory Artistry, shipped client website capture.