---
title: "I Will build a Rust REST API or backend service with axum"
url: https://zinnhub.com/zinns/i-will-build-a-rust-rest-api-or-backend-service-with-axum/
description: "Rust REST APIs and backend workers built on axum, delivered to your repository with tests and a README. Fixed scope per tier, written updates, no calls."
published: 2026-09-28T16:42:08+00:00
modified: 2026-09-30T08:13:00+00:00
language: en-GB
---

# I Will build a Rust REST API or backend service with axum

Your service arrives in your own repository with tests and a README, ready to run: a REST API on axum, a worker that processes files or a queue, or a service that sits between your system and someone else’s API. I came to Rust after eight years of web work, and I maintain reqwest-rotate, an open-source Rust crate on crates.io with docs, CI and about two hundred tests.

Starter is one service with up to 3 REST endpoints, or one worker reading files or a queue you already run: tests, a README, and source in your repository. No database schema work in Starter. Standard adds up to 8 endpoints, PostgreSQL or SQLite with migrations, input validation, integration tests against a test database, and a Dockerfile. Advanced goes to 15 endpoints and brings token auth with roles, a background worker, a CI workflow that builds and tests on every push, and a deployment checklist for your server.

Endpoints count as method plus path: GET /orders and POST /orders are two. Not included: a front end, a mobile app, or smart contracts.

Every service runs on Tokio, the async runtime axum is built on. Nothing ties it to one host: it runs on a Linux VPS, in Docker on AWS, Railway or Fly.io, or on your own machine. The Dockerfile comes with Standard and Advanced, and the Advanced deployment checklist is written for the server you name.

Written updates each working day on a multi-day build, fast replies, no calls.

Steps for completing your project
1. Scope confirmed in writing – I read your requirements and confirm the endpoint list, the tier fit and the stack before any code. Endpoints count as method plus path.
2. Repository, CI skeleton and data model – The project skeleton with the first endpoint working end to end, so you can see the shape of the service early and correct the direction while it is cheap.
3. Endpoints or worker, with tests – The remaining endpoints or the worker, each with its tests. On a multi-day build you get a short written update every working day.
4. Integration tests, README, Dockerfile – Integration tests against a test database, the README, a Dockerfile on Standard and Advanced, and a deployment checklist on Advanced.
5. Handover in your repository – Source delivered in your repository with a written handover: how to run it, how to test it, how to deploy it.