ForumBotMini app
Forum “Internet Safety School 4.0”
A bot and a mini app for all five days of the forum.
- 3 access levels
- Schedule
- Participant ranking
- Personal account
- Feedback
- Mass mailings
- Admin panel
Custom Backend Development: APIs and Integrations with 1C, CRM and Payments
We build the server side of an app: APIs, integrations with 1C (the most common accounting system in Russia), amoCRM, Bitrix24, YooKassa and SBP (Russia's instant payment system), and high-load systems. We write in Go, Python, Node.js and other languages that fit your task. An API for an app costs from $1,000 and takes 2–4 weeks. We hand over the source code and documentation.
- from $1,000 cost of an API for an app
- from 2 weeks timeline for an API or integration
- 24/7 monitoring after launch
- 3 months of free bug fixes
Business goals
What backend and integration development gives your business
The backend is the server side of an app. Customers never see it. Orders, payments and accounting stop without it. We build it to order and connect it to the programs you already use.
- API development for an app, a website and bots
An app screen needs an API (a set of commands it uses to talk to the server). We write it together with documentation. One backend can serve bots in Telegram, VK and the MAX messenger: the users are shared, and the data syncs in real time.
- 1C integration
Orders, customers and stock data go from your website or bot into 1C (the most common accounting system in Russia, used for goods and stock) without manual entry. Your staff do not have to retype spreadsheets.
- amoCRM and Bitrix24 integration
Requests from your website, bot and app show up on their own in amoCRM or Bitrix24 (popular Russian CRM systems for tracking customers and deals). The manager sees each request right away.
- YooKassa and SBP integration
We accept payments on your website, in a bot and in an app: YooKassa and CloudPayments (card payment services), SBP (Russia's instant payment system), Telegram Stars. The payment status shows up in the order right away.
- High-load systems
If a service has to handle many users at once, we design it for the load up front. We check this with load testing (we simulate a rush of users) before launch.
- AI in your service
We connect the YandexGPT, GigaChat and OpenAI API neural networks: answers to customers based on your documents (the RAG method), speech recognition. We calculate the price from the brief.
In plain words
The server side of an app: how it works
The easiest way to understand a backend is a restaurant.
A guest sees the dining room, the menu and the waiter. In an app, these are screens, buttons and pages. The guest never sees the kitchen. That is where the order is cooked, the stock is tracked and the dish goes out to the dining room. The backend is the kitchen of your service.
It takes requests from a website, bot or app, stores data in a database (a program that holds customers, orders and payments) and sends a response back.
What happens when a customer taps “Pay”
From here, the backend takes over. Here are six steps the customer never notices.
- Order check
The server checks the order: the price, the contents and whether it has already been paid. A mistake in the order is caught before any money is charged.
- Request to the payment system
The server sends the amount and the order number to YooKassa, CloudPayments or SBP.
- The customer pays
The customer confirms the payment in a banking app or on the payment system's page.
- Reply from the payment system
The payment system tells the server the result: the payment went through or it did not. The server checks that the reply really came from it.
- Saving to the database
The server saves the payment in the database and changes the order status to “paid”.
- Notifications
The customer gets a message about the payment, and the manager gets a notification about a new order. If needed, the data goes to 1C or the CRM.
Prices and timelines
How much backend and integration development costs
Below are starting prices. We fix the final amount in the contract after the brief (a description of your task), and it does not change after that.
| What we build | Price | Timeline | What's included |
|---|---|---|---|
| API for an app | from $1,000 | 2–4 weeks | The server side for a mobile app, website or bot, with OpenAPI documentation. |
| Integration with 1C, a CRM, payments and a warehouse | from $1,300 | 2–5 weeks | Data exchange between your system and 1C, amoCRM, Bitrix24, YooKassa, SBP or a warehouse. |
| High-load service | from $5,600 | 8–16 weeks | A service for a large flow of users, load testing, monitoring. |
The price in the contract does not grow. Rush work costs about 25% more and shortens the timeline by about 20%. Dollar amounts are approximate: our prices are set in rubles.
What affects the price
- The number of systems to connect: 1C, a CRM, a payment system, a warehouse.
- The complexity of the rules: discounts, order statuses, staff roles.
- The expected number of users and the load on the server.
- The state of the systems we have to connect to: whether they have documentation and access.
- Urgency: rush timelines cost more.
Reliability
Backend reliability: monitoring, backups, load tests
A server failure stops sales. We build reliability in from the first stage of development.
- 24/7 monitoring
We watch the server around the clock. Alerts (signals about problems) arrive in Telegram.
- Daily backups
We copy the database every day. If something breaks, the data can be restored.
- Load tests before launch
We check how many users the system can handle and find weak spots before launch. Pages and screens open in under a second.
- Automated tests and a one-minute rollback
The code goes through code review (a check by a second developer) and automated tests. Updates ship through CI/CD (automatic checks and deployment). If a new version works badly, we roll it back in a minute.
- Documentation, so you do not depend on us
We describe the API in the OpenAPI format (a common standard any developer understands). We hand over the source code and access, so another developer can continue the work without us.
- Data under 152-FZ
We store personal data in line with 152-FZ (Russia's personal data law). We host the system in Yandex Cloud, Selectel, Timeweb Cloud or on your servers.
Process and guarantees
How the work goes and what guarantees you get
Six stages. At each one it is clear what we do and how long it takes.
- Intro · 1 day
A chat in Telegram or a 30-minute call. You describe the task in your own words, and we write the technical specification.
- Prototype and estimate · 3–5 days
We show a prototype of the future system and put together an estimate.
- Design · 1–3 weeks
If the system has screens, such as an admin panel, we draw them before development. Two rounds of revisions are included in the price.
- Development · stages of 1–2 weeks
Every 1–2 weeks we show a working build (demo). We start the next stage after you accept the work.
- Testing and launch · about 1 week
We test the system under load and deploy it to the server.
- Support and development · by agreement
24/7 monitoring, alerts in Telegram, a monthly report. We develop the system when new tasks come up.
What we put in the contract
- NDA before we discuss your idea
We sign a non-disclosure agreement before you tell us the task.
- Price and timeline in the contract
The amount and the timeline are fixed in the contract and do not grow during the work.
- Staged payment
You pay for the next stage after you accept the previous one.
- Code, access and documentation
We hand all of it over to you. The rights to the code are written into the contract.
- 3 months of free fixes
We fix bugs found after launch for free for three months.
- The prototype stays with you
If you decide to stop after the prototype, it stays with you.
Examples of work
Projects where the server side works behind the screens
Behind the screens of these projects, a server side stores participant data, tells access levels apart, handles payments and bonuses, and sends mailings. A mini app is an app that opens inside a messenger.
Business clubMini app
Business club mini app
An app for club members with profiles and payment.
- Booking
- Member search
- Profiles
- Payment
RestaurantWebsiteMini app
Restaurant and billiards venue in Moscow
A website and a booking mini app with a loyalty card.
- Booking
- Bonuses
- Personal offers
- QR scanning
The home page has the studio's own demos: the Grain coffee shop Mini App, the Linen Studio booking bot, the game “Tower” and others. None of them is a client project. You can open them and try them.
Technology
Backend in Go, Python, Node.js and other languages
We choose the language and tools to fit the task and the systems we need to connect to. We pick from our own stack: Go, Python, Node.js, Java, Kotlin, C#/.NET, PHP, Rust.
Go suits services with a large flow of requests. Python is handy for working with data and for quick prototypes. We pick Node.js when it is convenient to write the website and the server in one language.
PostgreSQL stores the main data, and Redis speeds up frequent requests. Kafka and RabbitMQ line tasks up in a queue so the server does not get overloaded.
- Go
- Python
- Node.js
- Java
- Kotlin
- C#/.NET
- PHP
- Rust
- PostgreSQL
- ClickHouse
- Redis
- Kafka
- RabbitMQ
- Docker
- Kubernetes
- OpenAPI
- YooKassa
- CloudPayments
- SBP
- Telegram Stars
- YandexGPT
- GigaChat
- OpenAI API
- 1C
- amoCRM
- Bitrix24
- Yandex Cloud
- Selectel
- Timeweb Cloud
Questions
Frequently asked questions
Didn't find the answer? Message us on Telegram and we'll figure it out together.
How much does backend development cost?
An API for an app starts at $1,000 and takes 2–4 weeks. An integration with 1C, a CRM, payments or a warehouse starts at $1,300 and takes 2–5 weeks. A high-load service starts at $5,600 and takes 8–16 weeks. We fix the final price in the contract after the brief, and it does not grow. Rush work costs about 25% more and shortens the timeline by about 20%.
What do I need to start if I already have a working system?
Describe the task in your own words: what the system should do and which programs it needs to connect to. The intro takes one day: a chat in Telegram or a 30-minute call. We write the technical specification ourselves, and we sign an NDA (a non-disclosure agreement) before we discuss your idea.
Access to your system and its documentation, if you have any, will help.
Who owns the code, and can I work without you later?
We hand over the source code, access and documentation, and the rights are written into the contract. We document the API to the OpenAPI standard, so another developer can continue the work without us. If you want, we stay on for support by agreement.
Who watches the server after launch?
For three months after launch, we fix bugs for free. After that, support and development by agreement: 24/7 monitoring, alerts in Telegram and a monthly report. We back up the database every day.
Can you connect 1C, amoCRM or Bitrix24 to a website that already works?
Yes. An integration with 1C, a CRM, a payment system or a warehouse starts at $1,300 and takes 2–5 weeks. We discuss which data to pass and in which direction at the intro, and we fix the price in the contract.
Which language will the server use, and where will it run?
We pick the language for the task from our own stack: Go, Python, Node.js, Java, Kotlin, C#/.NET, PHP or Rust. For data storage we use PostgreSQL, ClickHouse or Redis.
We host the server in Russian clouds (Yandex Cloud, Selectel, Timeweb Cloud) or on your servers. We store personal data in line with 152-FZ (Russia's personal data law).
Other services
Let's talk
Tell us about your idea. Within one business day we will send a plan and an estimate
Keep it short, in your own words. We'll ask a few questions and suggest two or three options for different budgets.