Direction
Django platform development
Django is the studio’s stack for business applications: models, roles, an API, background jobs, and production support.
Request a callback
To make the request more precise — pick a Django direction in the tree nearby.
What Django business applications include
A backend, user cabinets, a back office, a REST API, and an admin. Cargo CRM, HomeBoard, and RiskBoard run on Django. SecBoard runs on Django with Celery and Redis. HomeBoard adds Channels, Daphne, and WebRTC.
How Django backend development is delivered
Architecture and a brief, a working demo, then deploy: Gunicorn or Daphne, a database, a domain, SSL, and monitoring. Live products use MySQL or PostgreSQL, depending on the project.
When a blank Django build is the slow path
Records, roles, task queues, Telegram, and reports fit Django well. If you need an information security platform or a logistics CRM that already exists, start from SecBoard or Cargo CRM — their modules are already in production use.
Questions
- Do you only build the Django backend? No. Django backend development here includes cabinets, an API, bots, and the production launch.
- Which databases do the live products use? SecBoard, Cargo CRM, and HomeBoard use MySQL. RiskBoard uses PostgreSQL. Queues, where the product needs them, run through Celery and Redis.
- Is there a mobile client in this stack? Yes, where the product needs one. HomeBoard has the HomeBoard Camera Android app, which connects to the Django cabinet.
- Where can I see a live Django product? In Projects: Cargo CRM, HomeBoard, RiskBoard, and SecBoard. The cards link to a demo or the official site.