Services/Web Development/Back end
Back-End Development
The server side of web and mobile products: APIs, databases, integrations and admin panels. We write it in Go, Python, PHP, C# and Node.js.
Which language fits your back end?
We choose the language for the task, not the other way round. These are the five we work in.
Go
by GoogleA compiled language built for services that handle many requests at once and stay cheap to run.
- Gin
- gRPC
- The system is split into services that talk to each other
- Thousands of users or devices are online at the same time
- Response time and server costs matter from day one
Python
Django, FastAPI and FlaskThe shortest way from an idea to a working back end, and the language of machine learning and data.
- Django
- FastAPI
- Flask
- The product uses AI, recognition or data processing
- You need an MVP with an admin panel quickly
- The team will later hire from a large pool of developers
PHP
Laravel, Symfony and YiiThe most common language of the web, with mature frameworks for platforms, portals and online stores.
- Laravel
- Symfony
- Yii
- You are building a web platform, a marketplace or a store
- An existing PHP system has to be extended or modernized
- Hosting and support should stay simple and inexpensive
C#
.NET and ASP.NET CoreMicrosoft's platform for business systems: strict typing, long support cycles and close ties with Azure.
- ASP.NET Core
- Entity Framework
- The rest of your systems run on Microsoft technology
- The product has complex business rules and many integrations
- Mobile or desktop apps in C# should share code with the server
Node.js
JavaScript and TypeScriptJavaScript on the server: one language for the front end and the back end, and a good fit for real-time features.
- NestJS
- Express
- Your front-end team should be able to work on the server too
- The product needs chats, live tracking or notifications
- A light API for a web or mobile app is all you need
What a back end consists of
The parts users never see, and what each of them does for the product.
Back ends we have built. Each case shows the stack, the task and what was hard.
All case studies
PythonTruck parts identification appA Python back end that names heavy-truck parts from photos with a vision model and fixed rules.Computer vision · Python · Flutter
GoTaxi fleet platformA subscription platform for taxi fleets: dispatching, pricing and payments on Go services.Go · Flutter
PHPABC Stars online English schoolLive video lessons, scheduling and parent reports on Laravel.Laravel · PHP
Engagement models
Three ways to work with us. We help you pick one on the first call.
Our engineers work as an extension of your team, under your lead or ours.
We agree on the scope, the price and the deadline before the work starts.
You pay for the hours worked and change priorities whenever you need.
We turned to the 24Gen team when the project was in a critical stage. Deadlines were looming, and the product was far from ready. From the very beginning, we were impressed by the team's professionalism and accountability. In a short time, they assembled an MVP, set up scrum processes, and introduced an AI-based solution for moderation. Despite tight deadlines, all key modules were delivered on time and with solid quality. We are very satisfied with the collaboration and confidently recommend 24Gen as a reliable partner for large-scale projects.
Watch the video
From our blog
All articlesWhich language do you recommend for a new back end?
It depends on the product. Go for systems with many services and high load, Python when the product involves AI or needs a fast start, PHP for web platforms and stores. If your team already works in one of them, we usually stay with it.
Can you build only the back end for our app or our front-end team?
Yes. We agree on the API with your developers first and document it, so both sides can work in parallel.
Can you take over an existing back end?
Yes. We start with a code audit to see what the codebase can support, then propose a plan for what to keep and what to rebuild, and start once you approve it.
Will the system cope when the number of users grows?
We ask about the expected load at the start and design for it. Before the launch we test the system under that load and show you the result.
Where will the back end be hosted?
In the cloud you choose, for example AWS or Azure, under your own account. The servers and the data stay yours.
How do you estimate the cost?
After the first call we break the task into parts and send you a written estimate. When the scope is clear, we fix the price and the deadline. When it is open or likely to change, we work on time and materials or as a dedicated team.
Who owns the code? Do you sign an NDA?
You do. The code and all rights to it pass to you in full. We sign an NDA whenever you need one.
Tell us about your product
Describe the task in a few lines. We will get back to you to set up a call.
info@24gen.space



