AKT
Hire Me
←Back to Blogs
Open Source

Open-Sourcing Solvia: An AI-Powered, Multi-Tenant Customer Support Platform

Today, FREMN is open-sourcing Solvia, an AI-powered, multi-tenant customer support platform built with Next.js, Convex, and Clerk. Solvia represents the foundation of FREMN's technical architecture and commitment to giving back to the developer community.

By Amar Kumar Thakur•

OPEN-SOURCING SOLVIA: AN AI-POWERED, MULTI-TENANT CUSTOMER SUPPORT PLATFORM

Amar Kumar Thakur 6 min read · August 2026

INTRODUCTION

Today, FREMN is open-sourcing Solvia, an AI-powered, multi-tenant customer support platform built with Next.js, Convex, and Clerk. Solvia represents the foundation of FREMN's technical architecture, the infrastructure patterns we developed while building, and our commitment to giving back to the developer community.

This decision reflects our belief that sharing production-grade code accelerates learning, attracts aligned contributors, and builds stronger engineering teams.

THE STORY BEHIND SOLVIA

Solvia was the first substantive product we built at FREMN. Before we pivoted to WhatsApp-native front desk automation for dental clinics, Solvia served as the proving ground for:

  • Multi-tenant SaaS architecture
  • Real-time AI agent infrastructure
  • Seamless AI-to-human escalation workflows
  • Production-grade customer support systems

While FREMN's focus has shifted to solving the specific problem of front desk automation in healthcare, the Solvia codebase remains stable, battle-tested, and—more importantly—educational. It's a non-trivial reference implementation of modern fullstack patterns.

We're releasing it under the MIT license because we believe valuable code should be accessible, and because contributors to this project may become part of the FREMN team.

WHAT IS SOLVIA?

Solvia is a scriptable AI customer support widget that integrates into any website with a single script tag. The core functionality:

  • Retrieval-Augmented Generation (RAG): Solvia answers customer questions directly from your team's knowledge base
  • Intelligent Escalation: When Solvia cannot help or a customer requests human assistance, it escalates with explicit context
  • Operator Dashboard: A real-time interface for support staff to take over conversations, view customer context, and manage sessions
  • Session-Based Widget Authentication: Secure, session-bound access to the embedded widget
  • Voice Support: Full voice conversation capabilities for customers who prefer speaking

The key architectural decision: escalation is not a fallback. It's a first-class feature with proper handoff semantics. When a customer needs a human, they get one—not a generic "I don't know" message.

Live Demo: https://solvia.fremn.com

TECHNICAL ARCHITECTURE

Solvia demonstrates production patterns across the modern JavaScript stack:

FRONTEND STACK

  • Next.js 14+ (React framework with App Router)
  • TypeScript: Full type safety across the codebase
  • Tailwind CSS: Utility-first styling for the operator dashboard
  • shadcn/ui: Composable UI components built on Radix
  • Real-time Updates: Server-sent events (SSE) for live conversation updates

BACKEND & INFRASTRUCTURE

  • Convex: Real-time backend platform for data synchronization
    • Instant database subscriptions for multi-user dashboards
    • Function-based backend eliminating server configuration
    • Automatic scaling and deployment
  • Clerk: Authentication and user management
    • OAuth integration for team onboarding
    • Session management for widget security
    • Role-based access control for operators

AI & NLP

  • Retrieval-Augmented Generation (RAG): Document-based knowledge retrieval
  • Language Model Integration: Integration points for LLM providers
  • Voice Processing: Speech-to-text and text-to-speech infrastructure

DEPLOYMENT & TOOLING

  • pnpm: Fast, disk-space-efficient package manager
  • Build & Lint: TypeScript compilation with tsc, linting with ESLint and Prettier
  • No Automated Test Suite: Currently relies on manual validation with pnpm build and pnpm lint
  • Manual Convex Deploys: Backend deployments are currently handled manually rather than through CI/CD

WHY OPEN SOURCE SOLVIA?

1. KNOWLEDGE TRANSFER

Solvia is a real, non-trivial codebase built for production. It serves as a reference implementation for:

  • Building multi-tenant SaaS systems
  • Integrating Convex for real-time backend architecture
  • Implementing secure widget-based auth flows
  • Designing AI agent handoff systems

There are many tutorials for simple projects. Production codebases that solve actual problems are rarer.

2. COMMUNITY CONTRIBUTION

We're looking for contributors who want to:

  • Add automated testing infrastructure
  • Enhance the escalation system
  • Improve knowledge base indexing and retrieval
  • Expand language support
  • Optimize performance

3. HIRING SIGNAL

When FREMN opens engineering positions, contributions to Solvia provide real insight into how someone thinks and works:

  • A bug fix demonstrates debugging methodology
  • A feature PR shows architectural understanding
  • A well-argued discussion reveals communication style
  • Consistency and attention to detail become visible over time

A contributor's history is worth more than a résumé.

CURRENT STATE & ROADMAP

STABILITY

The codebase is stable. We're no longer building the company around Solvia, but the code is production-ready and actively maintained. Critical bugs are reviewed and merged promptly.

QUALITY GATES

Code review process:

  • Manual validation with pnpm build (TypeScript compilation)
  • Linting with pnpm lint (ESLint + Prettier)
  • Review-driven merge process (no automated test suite yet)

This means the bar for contributions is clear but not automated. Contributions should compile cleanly, pass linting, and be well-argued.

INFRASTRUCTURE GAPS

Known limitations:

  • No automated test suite (contributors should add this)
  • Convex backend deploys are manual
  • No CI/CD pipeline for automated deployments

These are opportunities for contributors to make meaningful infrastructure improvements.

NEXT STEPS

  1. Community contributions and feedback
  2. Test suite implementation
  3. CI/CD pipeline setup for Convex
  4. Performance optimization
  5. Enhanced documentation for onboarding

TECH STACK REFERENCE

Frontend:

  • React 18+ (Next.js App Router)
  • TypeScript 5+
  • Tailwind CSS 3+
  • shadcn/ui

Backend:

  • Convex (real-time database & backend)
  • Clerk (authentication)
  • Node.js runtime

AI/ML:

  • Retrieval-Augmented Generation (RAG)
  • LLM integration points (OpenAI-compatible)
  • Voice API integration

Tooling:

  • pnpm
  • ESLint + Prettier
  • TypeScript compiler (tsc)

Deployment:

  • Vercel (frontend)
  • Convex Cloud (backend)
  • Clerk (auth)

GETTING STARTED

REPOSITORY

GitHub: https://github.com/thefremn/solvia

Fork the repository on GitHub, then clone and explore:

git clone https://github.com/YOUR-USERNAME/solvia.git
cd solvia
pnpm install
pnpm build
pnpm lint

CONFIGURATION

Environment variables required:

  • Convex API keys (from Convex dashboard)
  • Clerk publishable key (from Clerk dashboard)
  • LLM provider credentials (OpenAI, etc.)

RUNNING LOCALLY

pnpm dev

This starts the development server and watches for changes.

RUNNING QUALITY GATES

Before submitting a PR:

pnpm build   # TypeScript compilation
pnpm lint    # ESLint and Prettier

CONTRIBUTION GUIDELINES

We welcome contributions in the following areas:

1. TESTING & QUALITY

  • Add unit tests (Jest or Vitest)
  • Add integration tests for Convex functions
  • Improve type coverage

2. FEATURES

  • Enhance RAG document indexing
  • Add support for additional LLM providers
  • Expand widget customization options
  • Implement analytics and usage tracking

3. INFRASTRUCTURE

  • Set up automated test CI/CD
  • Configure Convex deployment automation
  • Add performance monitoring
  • Implement error tracking and logging

4. DOCUMENTATION

  • API documentation
  • Configuration guides
  • Deployment instructions
  • Architecture decision records (ADRs)

5. BUG FIXES

  • Any identified issues or edge cases

LICENSING & INTELLECTUAL PROPERTY

Solvia is released under the MIT License, permitting:

  • Commercial use
  • Modification
  • Distribution
  • Private use

With the requirement:

  • Include the original license and copyright notice

COMMUNITY & SUPPORT

Discord: Join the FREMN community on Discord (link in repository) GitHub Issues: Report bugs and request features via GitHub Issues GitHub Discussions: Engage with maintainers and other contributors

The maintainers review contributions regularly. Response time is typically 24-48 hours for active issues.

HIRING & CAREER OPPORTUNITIES

FREMN is actively hiring engineers. If you:

  • Contribute meaningfully to Solvia
  • Demonstrate strong architectural thinking
  • Write code that's maintainable and well-documented
  • Engage thoughtfully in code review discussions

We'd like to talk to you.

A single well-reasoned PR often reveals more about how someone works than any interview process.

CONCLUSION

Solvia represents FREMN's commitment to open source and to building the kind of engineering community we want to be part of. By sharing a production-grade codebase, we're giving back while also being transparent about how we build.

Whether you're learning modern fullstack patterns, looking for a real-world reference implementation, or interested in joining FREMN, Solvia is designed for you.

The barrier to entry is low. The learning opportunity is high. The potential to influence FREMN's engineering direction is real.

Clone the repo. Read the code. Submit a PR. Let's build together.

LINKS & RESOURCES

Live Demo: https://solvia.fremn.com GitHub Repository: https://github.com/thefremn/solvia FREMN Website: https://fremn.com Discord Community: [Link in repository]

Technology References:

© 2026 FREMN Technologies LLP Amar Kumar Thakur, Co-Founder & Full-Stack Engineer

End of article

Thanks for reading.

←All Articles