How dgree.io Built a Course Marketplace That Aggregates Thousands of Learning Options Into Personalized Paths
An EdTech startup needed to aggregate online courses from dozens of providers into one searchable marketplace with personalized learning recommendations. easy.bi built it from concept to launch using ElasticSearch, web scraping, and custom recommendation logic.
The Challenge: A Fragmented Learning Landscape With No Central Discovery
The online learning market is enormous - and fragmented. Thousands of courses exist across Udemy, Coursera, LinkedIn Learning, specialized industry platforms, and independent providers. For someone looking to learn a new skill, the problem isn't finding a course. It's finding the right course among thousands.
dgree.io's founders saw an opportunity: a marketplace that aggregates courses from every major provider into one searchable platform. Users would search once, compare options side by side, and start learning - without visiting 15 different websites.
The technical challenge was significant. Each course provider structures their data differently. Some offer APIs. Others don't. Course metadata - title, description, price, duration, skill level, language - varies wildly in format and completeness. Normalizing data from dozens of sources into a consistent, searchable catalog was the core engineering problem.
Beyond aggregation, dgree.io wanted personalization. Not just "courses like this" recommendations, but actual learning paths - sequences of courses that build on each other to take a user from beginner to competent in a specific skill area.
“Our users were opening 10 browser tabs to compare courses across different platforms. We wanted to replace those 10 tabs with one search bar.”
Why dgree.io Chose easy.bi
dgree.io was a startup with a strong vision and limited technical resources. They needed a development partner who could take a concept - sketched on whiteboards and validated through user interviews - and turn it into a working platform.
easy.bi proposed a full product development partnership: from concept refinement and prototyping through to a production-ready marketplace. The team's experience with ElasticSearch for complex search applications, web scraping for data aggregation, and ebiPlatform for rapid backend development meant dgree.io could work with one partner instead of assembling specialists from multiple vendors.
“We had a vision and user validation, but no technical team. easy.bi took our concept from whiteboard sketches to a production platform in 8 months. They weren't just developers - they were product partners.”
The Approach: Aggregate, Normalize, Personalize
The easy.bi team began by defining the concept alongside dgree.io's founders. User personas, core workflows, and technical architecture were established through collaborative workshops before any code was written.
Multi-source data aggregation. The team built a data ingestion pipeline that pulls course information from providers through two channels: API connections for providers that offer them, and web scraping for providers that don't. Each source feeds into a normalization layer that maps provider-specific data formats to dgree.io's common data model - ensuring consistent metadata regardless of origin.
ElasticSearch-powered discovery. The normalized course catalog is indexed in ElasticSearch, enabling sub-second search across thousands of courses. Users filter by topic, skill level, price, duration, language, and provider. Search relevance tuning ensures that the most applicable courses surface first - not just the most popular or most recent.
Personalized learning path engine. Beyond individual course search, the platform suggests learning paths: curated sequences of courses that progressively build a skill. The recommendation logic analyzes a user's stated goals, completed courses, and browsing behavior to suggest next steps. A user exploring Python programming sees a path from basics to data science to machine learning - with the best-rated course for each step pre-selected.
The frontend was built as a responsive web application using Angular and Vue for different platform components, with Ionic enabling a mobile-optimized experience. OAuth2 authentication through a custom ID service allowed users to save progress, bookmark courses, and maintain their learning history across devices.
“The data normalization was the hardest part. Every provider formats their course data differently. easy.bi built an ingestion pipeline that handles the mess - and gives us clean, searchable data on the other side.”
The Results: One Search, Thousands of Courses, Personalized Paths
dgree.io launched with courses aggregated from 20+ providers, searchable in under 200ms through ElasticSearch. Users who previously spent 30+ minutes comparing courses across multiple websites now find relevant options in a single search. The normalized data model means course comparisons are apples-to-apples - same metadata format regardless of the original provider.
The personalized learning path feature became the platform's differentiator. Users don't just find individual courses - they discover structured learning journeys. Early data showed that users who followed recommended learning paths completed 3x more courses than those who searched ad hoc.
The data ingestion pipeline proved scalable. Adding a new course provider requires configuring a new API connector or scraper - not architectural changes. dgree.io's team can onboard new providers independently, growing the catalog without engineering bottlenecks.
“Learning paths changed our retention metrics overnight. Users who follow a recommended path complete 3x more courses. That engagement data is what investors want to see.”
Key Takeaways
- Data normalization is the hidden foundation of aggregation platforms. The user sees a clean search interface. Behind it, dozens of different data formats are mapped to a common model. Investing in the normalization layer early prevents data quality issues from compounding as new sources are added.
- Personalization drives engagement more than catalog size. Users don't want more courses - they want the right courses in the right order. Learning path recommendations tripled course completion rates, proving that curation matters more than volume.
- Build the ingestion pipeline for extensibility. Adding new course providers should be a configuration task, not an engineering project. The API/scraping architecture allows dgree.io to grow their catalog independently - which is exactly how a startup needs to scale.
Ready to achieve similar results?
Speak directly with our experts. Book a 20-minute Expert Call.
Start with a Strategy CallProject Snapshot
More success stories
Multi-brand e-commerce platform with SSO for outdoor brands
Order processing middleware for multi-store Shopify operations