Forem: Light Speed Up

HealthForge: Proactive Wellness Kit Builder Powered by Algolia

Light Speed Up — Sun, 08 Feb 2026 03:24:40 +0000

This is a submission for the Algolia Agent Studio Challenge: Consumer-Facing Non-Conversational Experiences

What I Built

HealthForge is a non-conversational AI wellness kit builder that proactively assembles personalized fitness kits as users input their goals and preferences — no chat required.

The experience works in three steps:

Select Your Goals — Choose from 8 wellness objectives (weight loss, muscle building, endurance, flexibility, stress relief, better sleep, general fitness, recovery)
Set Preferences — Configure fitness level, allergies, diet, weather, budget, and indoor/outdoor preference
Get Your Kit — Instantly receive a curated kit of exercises, supplements, gear, and meal plans, with automatic compatibility checks

Key Intelligence Features:

Allergy auto-exclusion: Items containing flagged allergens are silently removed with clear alerts
Budget filtering: Items above your budget threshold are excluded
Diet matching: Meal plans filter by dietary preference (vegan, keto, mediterranean, etc.)
Equipment gap detection: If your exercises need a kettlebell but your gear section doesn't include one, you get an alert
Weather awareness: Outdoor exercises get flagged if they don't match your weather conditions

Demo

Live Demo: https://healthforge.vercel.app

GitHub: github.com/MatoTeziTanka/healthforge

Screenshots

Step 1: Goal selection with visual chips:
Users pick from 8 wellness goals — the selection drives every subsequent retrieval.

Step 2: Preference configuration:
Allergies, diet, budget, weather, and fitness level — each setting modifies the Algolia query.

Step 3: Auto-assembled kit with compatibility alerts:
The kit arrives pre-built with exercises, supplements, gear, and meal plans. Compatibility alerts flag issues proactively.

No login required. For quick demo: just select goals and preferences.

How I Used Algolia Agent Studio

Data Indexing

I indexed 110+ wellness items across 4 categories with compatibility-aware attributes:

{
  "name": "Kettlebell Swings",
  "category": "exercise",
  "subcategory": "strength",
  "difficulty": "intermediate",
  "calories_per_30min": 350,
  "muscle_groups": ["full body"],
  "equipment": ["kettlebell"],
  "goals": ["strength", "cardio", "functional fitness"],
  "allergens": [],
  "weather_suitability": ["any"],
  "indoor": true,
  "rating": 4.7
}

Each item carries compatibility metadata: allergens, equipment needs, weather suitability, diet type, and goal alignment. This enables the proactive intelligence that makes HealthForge more than just a search box.

Multi-Category Retrieval Strategy

Instead of a single search, HealthForge fires 4 parallel category-specific queries to Algolia using Promise.all():

const searchPromises = ['exercise', 'supplement', 'gear', 'meal_plan'].map((category) => {
  const categoryFilters = [[`category:${category}`]]
  if (difficulty !== 'any') {
    categoryFilters.push([`difficulty:${difficulty}`, 'difficulty:beginner'])
  }
  return searchClient.search({
    requests: [{
      indexName: 'healthforge_items',
      query: goals.join(' '),
      hitsPerPage: category === 'exercise' ? 5 : 3,
      facetFilters: categoryFilters,
    }],
  })
})

const allResults = await Promise.all(searchPromises)

All 4 searches fire simultaneously, ensuring each kit section gets dedicated retrieval with category-specific result limits and difficulty fallbacks — and the total build time is bounded by the slowest single query, not the sum of all four.

Post-Retrieval Intelligence

After Algolia returns the raw results, HealthForge applies 4 layers of proactive filtering:

Allergy exclusion: Cross-reference each item's allergens array against user selections
Budget enforcement: Remove items above threshold
Diet matching: Exclude meal plans that don't match dietary preference
Equipment gap detection: Compare exercise equipment needs against gear in the kit

All filtering happens client-side after Algolia's fast retrieval, keeping the experience responsive while adding personalization depth.

Search Configuration

Searchable attributes: name, category, subcategory, description, goals, muscle groups, benefits, diet type
Facet filters: category, subcategory, goals, difficulty, muscle groups, diet type, allergens, indoor, weather suitability, equipment
Custom ranking: rating (descending) — highest-rated items surface first within each category
Highlighting: name, description, goals, and benefits for context-rich result cards

Why Fast Retrieval Matters

HealthForge's non-conversational pattern demands invisible speed. Unlike a chatbot where users expect a moment for the "AI to think," a kit builder needs to feel like magic — you set preferences, and the kit appears instantly.

Here's why Algolia's speed is critical:

4 parallel category queries: Each preference change triggers 4 separate Algolia searches (exercises, supplements, gear, meal plans). At ~50ms each, the total kit builds in under 200ms. With a slower backend, users would see a loading spinner for each section.
Facet filtering depth: A single exercise query might filter by category:exercise + difficulty:intermediate + indoor:true + goals matching. Algolia handles this multi-faceted filtering in the same sub-50ms window.
Rebuild on adjustment: Users can tweak any preference and rebuild instantly. This "adjust and see" workflow only works when retrieval is fast enough to feel interactive rather than transactional.
Proactive alerts in real-time: The compatibility check (allergy conflicts, equipment gaps, weather mismatches) runs immediately after retrieval. If Algolia took seconds per query, the alerts would feel like a separate step instead of an integrated intelligence layer.

The result: HealthForge doesn't feel like a search tool. It feels like a personal trainer who already knows your preferences and assembled everything before you finished asking.

EcoVoyage AI: Sustainable Travel Companion Powered by Algolia

Light Speed Up — Sun, 08 Feb 2026 03:20:59 +0000

This is a submission for the Algolia Agent Studio Challenge: Consumer-Facing Conversational Experiences

What I Built

EcoVoyage AI is a conversational AI travel companion that helps users plan eco-conscious trips. Unlike generic travel planners, EcoVoyage puts sustainability at the center of every recommendation.

The agent guides users through natural dialogue to:

Discover 1000+ eco-rated destinations across 44 countries
Compare carbon footprints across 8 transport modes (train, bus, electric car, ferry, bicycle, sailing, hybrid car, and economy flight)
Find green accommodations with sustainability ratings (eco-lodges, treehouses, farm-stays, glamping, yurts)
Get personalized green offset tips based on their travel choices
Filter by budget, family-friendliness, season, and activities

Every destination includes a sustainability score, carbon footprint rating, and actionable tips to reduce environmental impact.

Demo

Live Demo: https://ecovoyage-ai.vercel.app

GitHub: github.com/MatoTeziTanka/ecovoyage-ai

Screenshots

The conversational interface searching for eco-friendly destinations:
The chat interface shows destination cards with sustainability scores, carbon meters, transport comparison charts, and green offset tips — all retrieved in under 50ms.

Key interaction flow:

User describes their dream trip ("eco-lodges in Italy")
Algolia instantly retrieves matching destinations from the indexed database
Results show with carbon comparisons, green features, and accommodation ratings
User can drill down into transport options or ask follow-up questions

No login required — try it immediately.

How I Used Algolia Agent Studio

Data Indexing

I indexed 1000 eco-travel destinations across 44 countries with rich, structured data:

{
  "name": "Tuscany Eco Beach Retreat",
  "country": "Italy",
  "region": "Tuscany",
  "sustainability_score": 8.7,
  "carbon_footprint_score": 2.3,
  "transport_options": [
    {"mode": "train", "carbon_kg_per_1000km": 14},
    {"mode": "ferry", "carbon_kg_per_1000km": 120},
    {"mode": "economy_flight", "carbon_kg_per_1000km": 255}
  ],
  "accommodations": [
    {"type": "eco-lodge", "green_rating": 5, "description": "Solar powered..."}
  ],
  "sustainability_features": ["solar powered", "zero waste policy"],
  "activities": ["kayaking", "olive oil tasting", "cycling tour"],
  "green_offset_tip": "Switch from flying to train to reduce emissions by 90%"
}

Search Configuration

Searchable attributes: name, country, region, category, description, activities, sustainability features, accommodation types
Facet filters: country, category, continent, season, price tier, group size, family-friendly, activities
Custom ranking: sustainability score (descending), then carbon footprint (ascending) — so the greenest destinations surface first
Highlighting: name, description, activities, and sustainability features

Two-Layer Algolia Integration

EcoVoyage uses Algolia in two complementary ways:

1. Conversational Search (Chat Interface)
Each message triggers an Algolia search via algoliasearch/lite. Results are processed into natural language responses with destination cards showing carbon comparisons, sustainability scores, and green tips. An autocomplete dropdown fires debounced searches as the user types, showing matching destinations in real-time.

2. Explore Section (InstantSearch Widgets)
A dedicated "Explore Destinations" section uses react-instantsearch with SearchBox, useHits, and Configure — providing a traditional search-as-you-type experience alongside the conversational interface.

Why Fast Retrieval Matters

Sustainable travel planning involves comparing multiple factors simultaneously: carbon footprint, sustainability score, transport options, accommodation ratings, activities, and budget. Users need to see these comparisons instantly to make informed decisions.

Algolia's sub-50ms retrieval makes this possible:

Real-time carbon comparison: When a user asks "compare train vs flight to Norway," Algolia retrieves matching destinations with transport data instantly, allowing the UI to render comparison charts without loading spinners.
Instant autocomplete: As users type in the chat, debounced Algolia queries return matching destinations in a dropdown — countries, regions, and destination names appear before the user finishes typing.
Sustainability-first ranking: With custom ranking on sustainability score, the greenest options always surface first. With Algolia, it happens on every query.
Multi-factor filtering: A single query can filter by country + category + season + budget + family-friendly, all with sub-50ms response times. This enables the conversational agent to narrow down from 1000 destinations to the perfect match in a single retrieval.

The speed isn't just a nice-to-have — it's what makes the conversational experience feel natural. Every message gets grounded in real, relevant data before the user notices any delay.

Launching LightSpeedUp: Hosting with network isolation - 70% cheaper than AWS

Light Speed Up — Tue, 04 Nov 2025 18:36:46 +0000

Hey Dev.to! 👋

I just launched my hosting platform with something unique: optional network isolation. Let me share the technical details.

🏗️ The Architecture

Community Shared Network (vmbr0):

Multiple customers on same network bridge
VM-level isolation with firewall rules between VMs
1 Gbps uplink
Perfect for 90% of websites

Isolated Network (vmbr[X]):

Your own private internal bridge per customer
10 Gbps internal bandwidth between your VMs
Complete network separation from other customers
PCI/HIPAA compliance-ready
Add $10/mo to any plan

🖥️ Hardware Specs

Dell PowerEdge R730
2x Xeon E5-2698v3 (32 cores, 64 threads)
480GB ECC DDR4 RAM
ZFS RAID-Z2 storage
Proxmox VE hypervisor

💡 Why This Matters

For a personal blog? Community Shared at $29/mo is perfect.

For e-commerce with PCI requirements? Business + Isolated at $99/mo gives you:

Dedicated network bridge
10 Gbps between your web server, database, and cache
Network-level isolation from all other customers

For agencies hosting multiple clients? Isolated Network means complete separation between client sites.

🔍 Complete Transparency

Live server stats: lightspeedup.com/health.php

You can literally watch CPU, RAM, and storage in real-time. No secrets.

💰 Pricing

Community Shared Network:

Starter: $29/mo (Beta: $14.50/mo)
Business: $89/mo (Beta: $44.50/mo)
Enterprise: $199/mo (Beta: $99.50/mo)

Isolated Network (+$10/mo):

Starter + Isolated: $39/mo (Beta: $19.50/mo)
Business + Isolated: $99/mo (Beta: $49.50/mo)
Enterprise + Isolated: $209/mo (Beta: $104.50/mo)

Compare to:

WP Engine Business: $25-290/mo
Kinsta Starter: $35-260/mo

30-70% cheaper with better hardware specs.

🎯 Technical Deep Dive

Why Proxmox instead of Docker/K8s?
Full VM isolation with KVM. Every customer gets their own kernel. Network isolation at the bridge level (vmbr0 vs vmbr[X]) instead of just iptables rules.

Why ZFS RAID-Z2?
Enterprise-grade data protection. Can lose 2 drives without data loss. Checksumming catches bit rot.

Why Dell R730 instead of cloud VPS?
Direct hardware control. No noisy neighbors. Fixed costs = predictable pricing.

Single point of failure?
Yes, and I'm honest about it. Daily backups to offsite storage. Disaster recovery plan in place. Working toward multi-server setup, but being transparent about current state.

🏗️ My Background

15 years enterprise IT. Designed data centers for First Data/Fiserv across 3 continents. Veteran-owned.

Got tired of seeing small businesses overpay for hosting with hidden fees and offshore support.

Wanted to prove enterprise infrastructure can run profitably at small scale with complete transparency.

🎉 Beta Program

50% off for 75 days
First 20 customers get lifetime 15% discount
Free migration from current host

💬 Questions I'll Answer

Network isolation architecture (vmbr0 vs vmbr[X])
Proxmox vs alternatives
Disaster recovery approach
Compliance considerations (PCI, HIPAA)
Why single server vs distributed
Backup strategy

Apply for Beta: lightspeedup.com/beta.php

Building in public because accountability matters. AMA! 🚀