Hire a Django developer, keep every line

We take on Django work for startups and product teams: features, APIs, upgrades and takeovers of code someone else wrote. You choose a fixed project or a monthly block of hours, the code lives in your repository, and the contract assigns it to you.

We work from India (IST, UTC+5:30) and keep a daily overlap with your mornings.

A pull request in our review tool: 'Move invoice emails to Django's background tasks', three files changed, the new task function and its enqueue call, 412 tests passed, approved by the client's CTO

Same developers, three ways to pay

Same people, same code standards. What changes is how the work is scoped and billed.

Who owns the code, put in writing

Under US copyright law, software written by a contractor isn't a work made for hire, so paying for it doesn't make it yours. That takes a signed assignment, and ours is in the contract.

  • Code in your repository from the first commit
  • Copyright assigned to you as each invoice is paid
  • Mutual NDA signed before we see the code
  • Open-source licences listed at handover
  • Our access removed in writing when we stop

Excerpt, our standard services agreement

Intellectual property

  1. 7.1

    Repository. All work is committed to repositories owned by the Client. Wingflows keeps no copy after handover beyond what the Client asks it to keep.

  2. 7.2

    Assignment. On payment of each invoice, Wingflows assigns to the Client all copyright and other rights in the work that invoice covers, and will sign any document needed to record the assignment.

  3. 7.3

    Open source. Third-party open-source components stay under their own licences, which are listed in the handover notes.

Draft wording for your lawyer to review; not legal advice. US Copyright Office Circular 30 explains why software needs an assignment.

4.2 and 5.1 are out of support

Django 4.2 and 5.1 no longer get security fixes. 5.2 does until April 2028 and 6.0 until April 2027. 6.1 is the current release, with full support until April 2027.

Dates from Django's supported versions table and release notes. See the upgrade audit price.

Client, Ohio

188 tests to 412, then 4.2 to 6.1

Lanternwick Analytics, Cleveland, Ohio

A B2B reporting SaaS stuck on Django 4.2 with thin test coverage. We added tests first, upgraded one release at a time to 6.1, and moved slow invoice emails to background tasks.

  • 188 to 412 tests
  • Five releases, no downtime
  • Code in their organisation
Upgrade plan from Django 4.2 to 6.1 in five steps, each with its Python version, test count, warnings fixed and live date, ending 3 November 2026
They started with tests around the billing module, which I'd been afraid to open since 2023. The week 6.1 went live we switched on the CSP middleware and closed an audit finding that had sat open for a year.

Django 4.2 to 6.1, PostgreSQL, Celery, Django REST Framework

Daniel OrtizCTO, Lanternwick Analytics

Django work we take on

Invoiced by us directly, no marketplace margin

You contract with us directly, so there's no marketplace margin on top. Euro prices are fixed too, not converted on the day.

Engagements

Invoiced in USD or EUR

Monthly block, 40 hours

A steady backlog, part-time

$1,900/month

€1,750 a month

  • Daily overlap with your mornings
  • Hours reported every Friday
  • One month's notice
Book a call →

Monthly block, 80 hours

Half a developer's month

$3,600/month

€3,300 a month

  • Daily overlap with your mornings
  • Hours reported every Friday
  • Planning call every two weeks
  • One month's notice
Book a call →

Fixed-scope project

A feature or app with a written spec

from
$3,000

from €2,800

  • Scope and estimate in writing
  • Paid per phase
  • Tests and handover notes included
Book a call →
  • Upgrade audit: $450 (€420), a written report on what moving to 5.2 or 6.1 involves.
  • Hosting and third-party services are billed by those providers.
Prices in US dollars and euros.Book a free 20-min call →
All articles →

CTOs tend to ask about the contract first

How much does it cost to hire a Django developer?

Monthly blocks start at $1,900 for 40 hours; fixed-scope projects from $3,000. You contract with us directly, with no platform fee on top.

Who owns the code you write?

You do. The contract assigns copyright to you as each invoice is paid, and the code sits in your repository from the first commit. Without a written assignment, US law doesn't make contractor-written software yours.

Will you sign our NDA?

Yes, before we see any code. We can also send our mutual NDA.

How many hours overlap with our time zone?

We work from India (IST) and keep a fixed window in your morning for calls and reviews: 9 to 12 Eastern, or most of a UK or European working day.

Can you take over an existing Django codebase?

Yes. We read it, add tests around what it does today, then change it.

We're on Django 4.2 or 5.1. Do we need to upgrade?

Yes, both are out of support. 5.2 gets security fixes until April 2028 and 6.1 is the current release. We upgrade one release at a time, with tests at each step.

Are you a Django development company or a marketplace?

A small development company. You talk to the people writing the code, with no account manager in between, and you sign one contract with us.

What happens when we stop?

One month's notice on monthly blocks. You get handover notes, and our access is removed in writing.

Sources: Django, supported versions; Django 6.0 released (djangoproject.com, Dec 2025); US Copyright Office, Circular 30: works made for hire.

Book a call →

Send us the repo, or just the problem.

We'll read it before the call and tell you how we'd approach it, and which of the three ways fits.

Free 20-min call
Your repo, your copyright. USD or EUR.Book a call →