Hire a freelance
Django developer.
Python and Django work, prepaid in Hour Blocks of 6, 12 or 24 hours. New builds on Django 5.2 LTS, REST Framework APIs, Celery pipelines, admin tooling that non-developers can actually use, and upgrades off versions that stopped getting security patches. The site you are reading runs on Django, deployed by us.
Within two business days
Your message goes straight to the studio. No sales queue, no account manager in between.
Prepaid Hour Blocks
Buy 6, 12, or 24 hours up front at $30/hr. Unused hours never expire.
10 live products
Python and Django running in production, including on this very domain.
You own the code
Full source, in your repository, with the reasoning written down. No lock-in to us or anyone else.
Django work, described
the way it actually goes.
Six kinds of job that make up nearly everything a Django developer gets asked for, with the detail that tells you whether we have done it before.
New builds and new features
A new Django project, or a feature inside one that already exists. The shape matters more than the speed: models that reflect the real domain, a settings layout that separates development from production without duplicating itself, and migrations that a second developer can run without asking you questions.
- Model design & safe migrations
- Class-based and function views, honestly chosen
- Forms, validation & permission checks
- Templates with HTMX or Alpine
- Tests with pytest-django or the Django runner
- Settings split, no secrets in the repository
REST Framework APIs
An API that a front end, a mobile app or a partner has to live with. DRF serializers that do not leak internal fields, viewsets that are paginated and filterable by default, token or session auth chosen deliberately rather than copied from a tutorial, throttling that fails with a useful message, and a schema that is generated from the code so it cannot drift away from it.
- DRF serializers, viewsets & routers
- Token, JWT or session auth
- Pagination, filtering & ordering
- Throttling & permission classes
- OpenAPI schema generated from code
- Versioning so you can change it later
Celery, scheduled jobs & data pipelines
Anything slow belongs off the request cycle: report generation, imports, document processing, LLM calls, email sends. We build Celery tasks that are safe to retry, so a network blip does not produce two invoices, with Beat schedules that record what they did and alerting when a task stops running rather than when it starts failing loudly.
- Celery with Redis or RabbitMQ
- Idempotent, retry-safe task design
- Celery Beat schedules with audit logs
- Chunked imports that survive restarts
- Dead-letter handling for poison tasks
- Worker supervision under systemd
Admin & internal tooling
The Django admin is the cheapest internal tool in the industry and most teams leave it at the defaults. Customised properly it replaces a whole back-office build: inline editing where the relationship demands it, list filters and search on the fields staff actually use, bulk actions with confirmation, read-only fields for the things nobody should be editing, and per-group permissions so support cannot delete an order by accident.
- Custom ModelAdmin, inlines & fieldsets
- List display, filters & search tuning
- Bulk actions with safe confirmation
- Group-based permissions for staff
- Admin actions that queue Celery work
- Query tuning so admin pages stay fast
Version upgrades & unpinning
Django 4.2 LTS left extended support in April 2026, which means a lot of running apps are now taking no security patches at all. Upgrades go one minor version at a time with the deprecation warnings turned into errors so nothing sneaks through, and the dependency wall - an unmaintained package pinning an old Django, an old Python, or psycopg2 - gets dealt with instead of pinned harder.
- Step-by-step upgrades to 5.2 LTS
- Deprecation warnings treated as errors
- Python 3.12 / 3.13 compatibility
- psycopg2 to psycopg3 migration
- Replacing abandoned dependencies
- A green suite before each merge
Deployment you can repeat
A Django app that only runs on the original developer's laptop is not finished. We set up the real thing: Gunicorn under systemd behind Apache or Nginx, static files collected and served by the web server rather than Python, Postgres with a restore you have actually tested, TLS renewal that is automatic, and a deploy that is a documented sequence rather than folklore.
- Gunicorn, systemd & reverse proxy
- Static & media serving done properly
- Postgres tuning, backups & restore drills
- Environment variables & secret handling
- Logging and error reporting
- A written runbook for your team
What lands in your repository.
The standing list for every Hour Block. Anything specific to your job gets added before the first hour is spent.
Reviewable commits
Small commits on a branch in your repository, with messages that explain the why. You can read any single step and revert it without unpicking everything after it.
Tests around the change
Tests covering what we touched, in whatever runner your project already uses. If there is no suite yet, these become the start of one rather than a separate project.
Migrations that go backwards
Schema changes arrive as migrations with a working reverse, and a warning on any operation that will lock a large table during deploy.
Config out of the code
New settings arrive as environment variables with documented defaults. Nothing secret goes into the repository, and DEBUG is never left on in a production settings path.
A deployment runbook
How to run it locally, how to deploy it, how to roll it back, and which commands to run when something looks wrong at two in the morning.
A support window
A short window after handover. If something breaks because of the change we made, fixing it is not billed as new hours.
Python in production,
including this page.
Client work stays under NDA, so what we show is what we run ourselves. We name the stack of each one exactly, including where it is not Django, so you can judge the fit yourself.
agicad.com
The site you are reading is a Django application: database-backed blog, contact pipeline with rate limiting and honeypot, structured data on every page, served by Gunicorn behind Apache. Its Core Web Vitals work is documented in the template comments, not in a testimonial.
About AgiCADSEO Wander
An internal tool on Python with a FastAPI backend, a React front end, and Celery plus Redis handling article generation and submission queues. Same Python background-task engineering as a Django and Celery build, in a different web layer.
Read the case studyTechPrognoza
A content site moved from a Hugo static build to Django without losing an article, with an importer that read the old front matter. Gunicorn behind Apache, the same deployment shape we would set up for you.
Read the case studyMost of our other products run on PHP, and we would rather you see that than a page claiming Django products that do not exist. Judge the products page on that basis.
Four steps, no discovery call
you have to sit through.
Tell us what the project is and what you need. After that it is commits and short written updates, not meetings.
Tell us the problem
A few sentences on what you have and what you need. Rough is fine - we ask the questions that matter and tell you honestly if it is not a fit.
Pick an Hour Block
Prepay a block of hours - 6, 12, or 24. The block is the budget: we work until it is used, or you top up.
Work in the open
Small commits against your repository, on a branch you can read, with what changed and why explained in plain language.
Handover and support
You get the source, a runbook covering local setup, deploy and rollback, and a short support window for anything the change itself caused.
Bought in
prepaid Hour Blocks.
No volume games and no agency margin on top. You buy the block of hours that fits the size of the job, so you know the number before we start rather than after.
Typically enough for a focused fix, a small feature, or an integration you are stuck on.
Start with StarterTypically enough for a working prototype, or one well-scoped feature built and shipped.
Start with StandardTypically enough for a larger build with integrations, auth, or billing wired in.
Start with ProEvery Hour Block is hours at $30/hr with no discount. It is a bucket of time, not a fixed-scope deliverable. Unused hours do not expire - roll them into the same project or a later top-up. If the work runs long, you buy another block; nothing is billed without you agreeing to it first.
Frequently asked.
Which Django versions do you work with?
Django 3.2 upwards in practice, with 5.2 LTS as the version we would put a new build on today. Django 4.2 LTS left extended support in April 2026, so if you are still on it you are running without security patches and that is usually the first thing worth fixing.
What is an Hour Block, and what if the job takes more or fewer hours?
An Hour Block is a prepaid block of hours: Starter is 6 hours for $180, Standard is 12 hours for $360, Pro is 24 hours for $720. It is a bucket of time, not a fixed-scope deliverable. Unused hours do not expire and roll into the same project or a top-up. If the work runs over, you buy another block, and nothing gets billed without you agreeing to it first.
Do you build APIs with Django REST Framework or something else?
Django REST Framework by default, because it is the thing your next developer will already know. If the project is API-only and performance-sensitive we will say so and suggest FastAPI instead, which we also build in. We would rather recommend the boring right tool than sell you the one we feel like using.
Can you do the background jobs and scheduled work too?
Yes. Celery with Redis or RabbitMQ, Celery Beat for schedules, and the boring parts that get skipped: tasks that are safe to retry, a dead-letter path for the ones that keep failing, and logging that tells you whether last night's run actually did anything.
Do you work on the front end of a Django project?
Yes. Server-rendered templates with HTMX or Alpine where that is enough, and a Vue 3 front end over a DRF API where it is not. We will usually push back on a single-page application for an internal tool, because templates are cheaper to maintain and faster to load.
Can you deploy it, or do you just hand over code?
We can deploy it. Gunicorn behind Apache or Nginx, systemd units, static files collected and served properly, Postgres, TLS, backups and a restart that does not need us. That is exactly how this site runs, and you get the runbook so your own team can do it next time.
Who owns the code?
You do, from the first commit. Everything lands in your repository under your account, with no license back to us and no hosted piece you have to keep renting from us.
How do we start?
Send a few sentences through the form on this page describing the project and what you need. You get a reply from us directly, usually within two business days, with questions, an honest read, and which Hour Block we think fits.
Tell us about your Django project.
What it does, which Django and Python version it sits on, and what you need built or unstuck. A few sentences is plenty - we read every message and reply within two business days with an honest read and the Hour Block that fits.
Prefer email?
[email protected]