Production web apps
Next.js, Tailwind, TypeScript, performance-focused UI, SEO fundamentals, contact flows, analytics, and real deployment plumbing.
I am Mateusz Reglinski, a web developer with Microsoft server-infrastructure experience, a freelance studio, and a workflow built around Next.js, automation, Linux, and practical AI agents.
const candidate = {
name: 'Mateusz Reglinski',
focus: ['web apps', 'automation', 'AI tooling', 'infra'],
ships: 'working links, not slideware',
defaultMode: 'build → verify → explain',
}
Next.js, Tailwind, TypeScript, performance-focused UI, SEO fundamentals, contact flows, analytics, and real deployment plumbing.
I use Claude Code, Codex, Hermes, MCP workflows, and structured reviews to ship faster without turning the codebase into soup.
n8n workflows, lead handling, reporting, CRM-style glue, email flows, scraping where legal, and small internal tools that remove repetitive work.
Linux, Docker, Dokploy, Traefik, Cloudflare, Tailscale, hardened VPS setups, monitoring basics, and pragmatic production ops.
case snapshots
Not everything can be public, and I am not going to invent fake metrics for recruiter candy. These are truthful snapshots of the kind of systems I build and operate.
A live freelance site that combines custom design, service positioning, blog content, contact conversion, and an embedded AI assistant.
Proof angle: You are looking at it. The site is the product, not a screenshot pretending to be one.
A clean local-business website for a handyman service with service pages, fast browsing, mobile-first layout, and direct enquiry paths.
Proof angle: Real client-style service site focused on clarity and enquiries rather than design-dribbble theatre.
A self-hosted assistant workflow using Hermes Agent, OpenRouter, Telegram delivery, persistent memory, cron jobs, and server-side tooling.
Proof angle: This is how I run planning, research, coding support, backups, and operational reminders across my own work.
Workflow designs for document creation, tenant reporting, summaries, and structured business data handling.
Proof angle: Practical automation for repetitive admin work, kept honest and grounded in real use cases.
workflow
I am useful in the gap between “we need something” and “there is a working system people can use”. That gap is usually where projects go to quietly die.
I turn fuzzy requirements into a visible workflow: users, inputs, outputs, edge cases, risks, and what can be shipped first.
I prefer small working releases over huge hidden rewrites. Web page, dashboard, API route, agent tool, automation; whatever proves the value fastest.
Builds, linting, screenshots, logs, test fixtures, working links. If it was not exercised, it is not done. Novel concept, apparently.
I document how it works, what it does not do, where secrets live, and how someone else can safely operate it later.
Send the role, the messy requirement, or the thing your team keeps doing manually. I will tell you directly if I am a fit. Dangerous concept: honesty.