Daphnis Labs
AI & Product Engineering

PourBud

Drink discovery, pricing and planning for India

A complete consumer platform connecting city-wise drink data with AI, regional stories and community.

The project

Prices and availability vary by location. Daphnis built PourBud around that challenge, with a shared data foundation for its public experience and administration tools. The platform supports discovery and education for adults of legal drinking age; it does not sell or deliver alcohol.

Industry
Beverage discovery
Our role
Full-stack product developmentAI & data workflowsSEO engineeringUX & authentication
Technology
Next.jsNode.jsPostgreSQLPrismaFirebase
AI deployment
Self-hosted

Inside the PourBud experience

Compare the product details

Each drink page brings its description, size and local price context together, with related products for further exploration.

Explore this page (opens in a new tab)

Learn with Guides

Editorial pages explain categories, labels, mixers and food pairings, connecting beginner questions with relevant drinks and responsible hosting advice.

Explore this page (opens in a new tab)

Explore regional drinks with Atlas

Profiles such as Mahua, Toddy and Apong connect ingredients and traditions with their regions. Place-based trails make India's drink culture a separate way to explore.

Explore this page (opens in a new tab)

Plan around guests and budget

Party Planner uses preferences, guest needs, estimated quantities and city pricing to shape a practical drinks plan. A login lets users save their preferences.

Explore this page (opens in a new tab)

Ask the Community

Topic-based discussions cover beginner questions, beer, whisky, food pairings and regional drinks, with reporting and moderation supporting the conversation.

Explore this page (opens in a new tab)

Keeping drink data current

A continuous data pipeline supports the catalogue as prices, products and locations change.

  1. Collect from verified sources

    Automated scraping and updates draw on government excise data and other verified public sources.

  2. Structure for each location

    Organise products, categories and bottle sizes, keeping city pages consistent where state-level pricing applies.

  3. Maintain through the admin

    Manage catalogue records, cities, Guides and Atlas entries from shared tools, without editing every public page separately.

A bottle photo becomes a starting point

  1. Understand the bottle

    Use the image as an input for product information and explanations.

  2. Explore ways to serve it

    Bring recipes and serving ideas into the same discovery experience.

Search architecture built into the product

City, category, product and guide pages use dedicated metadata, canonical URLs and internal links. A sitemap index and child sitemaps support discovery as the catalogue grows; robots and noindex controls keep low-value pages out of search. Breadcrumb schema and product schema use the information available for each page.

Google or mobile OTP. One account

Firebase supports both sign-in methods, with optional account linking in either direction. The authentication work covers duplicate-account handling, OTP resend, clearer errors and reCAPTCHA handling, so users can return to their saved preferences without being forced to add another login method.

What are you building?

Bring us your idea. We’ll shape the next step together.

Talk about your project

0 / 8
WhatsApp

Reviews

What our clients value about working with Daphnis Labs.

View All Reviews
View All Blogs

Blogs

Practical perspectives on AI, product engineering, commerce and modern software delivery.