client website [ live ]
Ink & Ivory Artistry
A South Perth nail studio that needed prices, policies and a booking path people can find on a phone. Shipped, indexed and in use.
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
01 // work
Every case links to a live product, a shipped site, or a public trail. Open it and check.
client website [ live ]
A South Perth nail studio that needed prices, policies and a booking path people can find on a phone. Shipped, indexed and in use.
owned product [ live ]
Self-hosted Polymarket trading automation. I own the product, the dashboard and the support surface, so status, controls and risk have to stay readable.
Open product ↗telegram bot [ live ]
Slow, risk-aware Polymarket automation in Telegram, built so the customer flow and the runtime state say the same thing.
Open product ↗public security work
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
Public pages beat invented case-study numbers. These links go to the real thing.
// public record
03 // services
You deal with the person inspecting, building and shipping the work.
Small business sites, product pages and focused landing pages. Mobile layout, working forms, DNS, performance, SEO basics and launch verification.
Start a job ↘Operator dashboards, customer controls, state recovery and runtime validation for automation that cannot hide behind a pretty mock-up.
Start a job ↘Practical contract and application review with tight scope, exact state analysis and evidence you can reproduce.
Start a job ↘Broken deploys, DNS and email routing, account state, browser-only workflows and neglected integrations where the truth is scattered.
Start a job ↘04 // process
A URL, access, the failure state and the result you want is enough to begin.
What is broken, what you expected, what access exists and when it matters.
I inspect the page, source, logs and account state before prescribing anything.
The work happens against the real system with checkpoints where risk warrants them.
You get the working result, proof it is live and notes that make it durable.
05 // contact
A screenshot, URL, repo path, login state, error message and deadline is enough to start.