Custom work

The software around the server.

Custom development is quoted separately from hosting, based on scope. Here is what we build, and roughly what each engagement involves.

Telegram bots

Bots that actually survive real users.

Inline keyboards, media handling, payments, admin tooling, channel posting, session handling and rate-limit discipline. Built to run unattended for months, not for a demo.

1–3 weeks typical

Typically includes

  • Inline ordering and admin dashboards
  • Media pipelines: video, audio, documents
  • Channel and story posting with scheduling
  • Payment gating, roles, per-user quotas
  • Deploy packaged with systemd + health checks

APIs & backend systems

The boring, correct part behind your product.

REST or GraphQL services with proper auth, migrations, rate limiting and observability. Designed so the next person can read it.

1–4 weeks typical

Typically includes

  • Auth, sessions, API keys and RBAC
  • Schema design, migrations, seed data
  • Rate limiting and abuse controls
  • Structured logs and health endpoints
  • Docker or PM2 deployment config

Scraping & automation

Reliable collection, not a brittle one-liner.

Resilient fetchers with retries, proxy rotation, request budgeting and structured output. Built to handle the target changing under it.

1–2 weeks typical

Typically includes

  • Rotating proxies and per-domain rate budgets
  • Retry, backoff and circuit breaking
  • Structured output: JSON, CSV, database
  • Scheduling, queues and failure alerting
  • Anti-dupe and deduplication logic

Websites & web apps

Fast, accessible, actually maintainable.

Marketing sites, dashboards and internal tools. Semantic markup, real SEO, fast first load, and a codebase you can hand to another developer.

1–3 weeks typical

Typically includes

  • Next.js / React front ends
  • Dashboards, admin panels, CRUD
  • SEO, sitemaps, structured data
  • Accessibility and mobile-first layout
  • Analytics, forms and email flows

Process

How a build actually runs.

  1. 01

    Discovery

    A short call or thread to establish exactly what needs to exist, who uses it, and what success looks like. Usually free.

  2. 02

    Scope & quote

    A written breakdown of deliverables, timeline and fixed price. You approve before anything starts.

  3. 03

    Build

    Short build cycles with something running early, so you can react to real output instead of a mock-up.

  4. 04

    Handover

    Source code, deployment config, documentation and a walkthrough. You own all of it.

Not sure what you need?

Describe it in plain language.

You do not need a technical brief. Tell us the problem you are trying to solve and we will tell you what it takes.