Services and ordering

I will build a website or service for your task

You describe the task, and I name the approach, the price and the timing for that task. You work directly with the person who writes the code.

Discuss your taskHow to orderSee the projects

What I do

Four areas. Each has live examples in the catalogue: open them and check.

Websites and landing pages, end to end

Who it is for

For businesses and freelancers who need a site for leads, bookings or presenting their services.

What you get

  • Responsive layout for phone, tablet and desktop.
  • A lead form or a contact button.
  • Metadata for search and social previews, fast loading.
  • An accessibility check: contrast, focus, keyboard.

Timing

A landing page: from 1 day to a week. A multi-page site: I name the time after the brief. The exact time depends on the task.

Backed by projects

Web apps and MVPs

Who it is for

For people testing an idea or replacing spreadsheets and chat threads with one working tool.

What you get

  • An app with sign-in, data and a server.
  • Offline mode (PWA) when the task needs it.
  • A first version you can collect user feedback on.
  • Code you can build on: structure, tests, README.

Timing

I name the time after the brief. The exact time depends on the task.

Backed by projects

Backend, API and VPS deployment

Who it is for

For products and teams that need an API, a job queue, authentication, integrations or webhooks.

What you get

  • A service in Go, Rust, Python or TypeScript with an API and a database.
  • Tests and CI: a check on every change.
  • Protection against common vulnerabilities: rate limits, input validation, secrets only in the environment.
  • Auto-deploy to a server and backups.

Timing

A backend project: from a week to a month. The exact time depends on the task.

Backed by projects

Tools and automation

Who it is for

For people who do the same thing by hand every week: parsing logs and tables, building reports, checking files.

What you get

  • A tool: one binary or script with clear flags.
  • Exit codes, so it fits into scripts and CI.
  • Help with examples and tests for edge cases.

Timing

I name the time after the brief. The exact time depends on the task.

Backed by projects

These are demos and concepts with fictional brands. I have no client list or testimonials, but every project can be opened and checked.

How the work goes

  1. 01

    Brief

    You describe the task on Telegram or by e-mail. I ask what is unclear: who it is for, what the result should be, what already exists.

  2. 02

    A quote for your task

    I name the scope, the price and the timing for your task. There is no price list: fixed tariffs do not fit tasks that differ.

  3. 03

    First version

    I show a working prototype or a first version. You can open and check it, and we discuss changes on the real thing.

  4. 04

    Development with tests

    I write the code together with tests and CI. You can look at intermediate versions along the way.

  5. 05

    Launch on a server

    I set up deployment, the domain and HTTPS, and backups where the project needs them. I hand over the instructions.

  6. 06

    Support

    Support on your domain or server. The price depends on the project. A warranty period for bug fixes: from one month to six, depending on the project.

What stays with you

This is how I always work. It is the way of working, not paid extras.

  • Code in your repository

    I work in your repository or hand over mine. The code is yours.

  • Documentation

    A README with the run steps, settings and limitations, like the catalogue projects have.

  • Tests and CI

    An automatic check on every change to the code.

  • Auto-deploy

    Deploys to the server happen on their own after a merge to the main branch.

  • Clear instructions

    How to run, update and restore from a backup, with no prior knowledge of my projects.

  • Access stays with you

    The domain, hosting and accounts are registered to you. I only need access while I work.

Why you can trust me

Only what you can check.

  • The catalogue has 50 projects, 43 of them live: open them and try for yourself.

    Open the catalogue →

  • 24 services run on my own VPS, the rest on Cloudflare.

    How it is built →

  • Every project has a repository, tests and CI. The Go projects have 418 tests and 230 routes. The repositories are private and open on request.

    Numbers by project →

  • Security is checked separately: CSP without inline scripts, SSRF protection, rate limits, containers without root. Every line rests on tests.

    The checks table →

  • My own algorithms instead of ready-made libraries where it shows the level of work: QR codes from scratch, a Markdown parser, Raft, SM-2 spaced repetition, a hash-chained ledger.

    The strongest projects →

  • Honest about the limits: I have no client list or testimonials and will not invent any. The projects in the catalogue are learning projects with fictional brands, but each one can be opened and checked.

    More about me →

Questions and answers

How do you price the work?

Per task. After the brief I name the scope and the price. There is no price list up front: a one-screen page and a service with authentication cost different amounts.

How does payment work?

An advance at the start of the work, the rest at the end. A landing page: a 20% advance, a large site: 50%. For backend projects and other tasks the advance is discussed per project. More on the How to order page.

How long does it take?

A landing page: from 1 day to a week. A backend project: from a week to a month. For multi-page sites, web apps and CLI tools I name the time after the brief. The exact time depends on the task and on how fast you provide materials and answers.

Who owns the code?

You do. I hand over the repository together with its history. We fix the handover terms before the work starts.

Can it run on my hosting or on your VPS?

Either way works: on my VPS or on your side. We choose for the task. I keep my own 24 services on my own VPS.

What about support after launch?

Support covers work on your domain or server, and the price depends on the project. After launch there is a warranty period for bug fixes: from one month to six, depending on the project.

What do you need from me as a client?

Describe the task and say who it is for. Provide materials if you have them: texts, a logo, access. Answer questions along the way. If you have no materials, I will tell you what to prepare.

Do you have testimonials or a client list?

No, and I will not invent any. But every catalogue project can be opened and checked: each has a repository, tests and CI, and 24 services run on my VPS.

How do I reach you and how fast do you reply?

There is no manager, you write to me directly: djrciv@gmail.com or Telegram @Ewsirdev. I usually reply within 5 minutes to an hour.

Describe your task: a couple of sentences is enough

What needs doing, for whom and by when. We will sort out the rest in the conversation.

Send an e-mailMessage on Telegram

There is no manager, I reply myself: Telegram or e-mail. Usually within 5 minutes to an hour.

Build a brief