Dropp took full ownership of software development, QA, and DevOps for Doukht Bartar—helping a 90,000+ learner platform launch new revenue features, establish controlled delivery, and sustain 99.95%+ uptime.
Discuss Your SystemDoukht Bartar is a specialized online learning platform for sewing and tailoring in Iran, serving more than 90,000 active learners with over 350 hours of video content and millions of monthly requests.
Its growth, however, was constrained by a recurring problem: even simple features could take months to deliver, accumulated technical debt slowed every change, and developer turnover repeatedly pulled management back into hiring and knowledge transfer.
In spring 2024, Dropp assumed end-to-end ownership of software analysis, frontend and backend development, the admin panel, QA, DevOps, and support. The result was more than a collection of delivered features. Doukht Bartar gained one accountable technology team—from architecture decisions to deployment and production health.
Doukht Bartar already had a strong visual experience and an established learner base, but its software carried substantial technical debt. The architecture was not ready for long-term growth, components were tightly coupled, and none of the applications had automated tests.
Every change risked creating regressions elsewhere. Straightforward features remained in development for months and sometimes reached production with defects. Meanwhile, recurring developer turnover forced the company to continuously recruit replacements and rebuild product knowledge.
For an education business, this was not merely a code-quality issue. It directly affected time to market, revenue opportunities, and management focus.
Instead of replacing a few individual developers, Doukht Bartar transferred technical ownership to Dropp. The delivery team included a Tech Lead, a Senior Backend Engineer, three Senior Frontend Engineers, a QA & Test Engineer, and the Dropp Tempo DevOps team.
Dropp brought requirements analysis, architecture, frontend and backend engineering, administration tools, testing, release management, and production support into one operating model. Doukht Bartar's own designer remained responsible for visual design, while Dropp turned those designs into reliable product capabilities.
Responsibility was no longer fragmented across individuals and vendors. The same team that designed and built a feature remained accountable for its quality and behavior in production.
Pausing the live product until a full rewrite was complete was not an option. Active learners still depended on the platform, and the business continued to need new capabilities. Dropp therefore ran two tracks in parallel: stabilizing and extending the existing platform while designing a microservices architecture for its next generation.
High-risk areas in the live system were incrementally refactored to accelerate change and reduce production risk. In parallel, the target architecture was designed and several independent services were completed, using PostgreSQL, MongoDB, Redis, RabbitMQ, and Object Storage where appropriate.
This approach allowed Doukht Bartar to keep serving customers, earning revenue, and shipping features instead of waiting years for a big-bang rewrite.
One of the clearest outcomes of the partnership was the creation of new revenue paths. Dropp developed a subscription model alongside individual course purchases, giving learners access to selected course libraries based on their subscription tier. The model did not replace one-time purchases; it added a complementary source of revenue.
The payment module and related shopping-cart flows were fully redesigned and rewritten. Their migration was executed without downtime, protecting the buying experience for active customers.
Integration with SnappPay added installment-based purchasing. The business outcome went beyond cleaner code: Doukht Bartar could test more commercial models and make its courses accessible to a broader group of learners.
Doukht Bartar needed more than a video storefront. Dropp built a social feed where learners can publish images and videos, like and comment on posts, and follow one another.
A question-and-answer experience further connects learners with the education team. Alongside it, the custom LMS controls access to more than 350 hours of video content for over 90,000 active learners according to purchases and subscription levels.
Together, these capabilities moved Doukht Bartar closer to an interactive learning platform where education, practice, and community live in one experience.
The inherited codebase had no automated tests. Dropp introduced automated testing, embedded QA into the delivery team, and established separate Test, Staging, and Production environments.
The CI/CD pipeline builds and scans the application, runs automated tests, backs up databases before deployment, executes database migrations, and then releases the new version.
This repeatable path increased delivery speed without trading away quality or recoverability. Every release follows a controlled process, and the team has visibility and a response path from the moment it reaches production.
Dropp Tempo had managed Doukht Bartar's DevOps since 2022. Services were containerized and deployed on an active-passive high-availability architecture using Docker Swarm. MySQL has a replica in a second data center, and a full database backup is created every six hours and transferred to Object Storage.
An automated daily control verifies that each backup was created, transferred successfully, and has a non-zero size. Quarterly recovery drills go further by testing whether the data can actually be restored.
Prometheus and Grafana monitor servers, resources, and endpoints; ELK centralizes logs; and Sentry tracks application errors. Alerts reach the customer channel in Mattermost, Dropp's internal Rocket.Chat, and customer email recipients. A 24/7 support team remains accountable for operational incidents.
Doukht Bartar serves more than 90,000 active learners and delivers more than 350 hours of video learning content. Its CDN layer records over 545,000 requests per day and approximately 16.4 million per month.
After frontend, backend, caching, and ArvanCloud CDN optimization, primary pages typically load in under two seconds for users in Iran. Technical issues identified by the SEO team were also resolved so the software itself would not block crawling, indexing, or page performance.
Across the measured 90-day window, the platform recorded uptime above 99.95%, supported by multi-layer monitoring, high availability, recoverable backups, and clearly owned incident response.
• Technical ownership moved from disconnected individuals to one accountable team • The customer no longer had to continuously recruit and replace developers • Feature delivery became faster and releases gained a repeatable quality path • Subscriptions created a complementary revenue stream • Payment and cart flows were rewritten and migrated without downtime • SnappPay installment payments expanded purchasing options • A social feed strengthened learner engagement • QA and automated testing became part of every release • A microservices foundation was designed for the platform's next generation • The platform sustained 99.95%+ uptime with 24/7 support
The most important result was confidence. Doukht Bartar's leadership could hand software and infrastructure needs to Dropp and keep its own attention on education, content, sales, and business growth.
Broader product development was temporarily paused in May 2026. The microservices architecture and several independent services were completed, but the full next-generation migration has not entered production. The infrastructure partnership continues, with Dropp Tempo still responsible for monitoring, backups, incident response, and 24/7 operations.
If a simple feature takes months to ship, your current codebase blocks growth, or management spends too much time hiring and coordinating technical staff, the problem is not just a shortage of developers. Your product needs an accountable technology owner.
Dropp can take responsibility for the complete product lifecycle—from analysis and architecture to frontend, backend, QA, DevOps, and production support. Start with a technical assessment and an actionable delivery roadmap.