From a business idea to a live car marketplace, in under five months.
Carbassador is a web platform where someone considering a car can chat privately with a verified owner of the same model. rinf.tech developed it end to end, from requirements through to production.
Development started in June 2025. The platform went live in November, under five months later, and is running in production in Norway.
A buyer comparing two cars can ask a salesperson or read reviews. The salesperson earns a commission on the sale, while a review rarely says how a model holds up in the buyer’s climate, on their roads, or after years of ownership. The people who know, the owners, have no structured way to be found or verified.
Carbassador makes verified ownership the basis of the marketplace: a buyer is matched with a real, checked owner of the same model, and the two chat privately. rinf.tech took the idea from requirements to a live product.
The platform shipped to production in under five months. In the August 2026 snapshot, 163 people had registered and 75.9% of non-administrator users had used the in-platform chat, with 467 messages exchanged across 93 buyer–owner connections.
Development start to production. From development start (June 2025) to the first production release (November 2025).
Used the in-platform chat. 123 of 162 non-admin users, in the August 2026 production snapshot.
Buyer–owner connections. With 467 messages exchanged, about five per connection. From the production database.
Buyers have no reliable way to reach real owners
A buyer comparing two cars can ask the salesperson or read reviews. The salesperson earns a commission on the sale. A review rarely explains how a specific model performs in the buyer’s climate, on their roads, or after years of ownership.
The people who do know, the actual owners, have no structured way to be found, verified, or heard. A review platform can confirm that someone left a rating. It cannot confirm that the person owns the car, or that the account belongs to a real person.
Carbassador’s answer is a role-based marketplace organized around verified ownership, with no review feed layered on top.
A stack chosen for speed, budget, and the team
The client brought a business concept, not a technical specification. The stack was rinf.tech’s recommendation, shaped by three pressures that pulled against each other: ship quickly, keep the platform maintainable, and do both on a limited budget, with a team that included six junior developers moving into full-stack roles.
The answer was a mainstream web stack, with sign-in and permissions kept separate from the core product logic, and automated, versioned releases from day one.
- Frontend · Next.js. What buyers and owners see in the browser. Mature enough to let junior front-end developers take on full-stack work over time.
- Backend · NestJS. The structured core behind the screens, handling data requests and real-time chat, with room for mobile and push notifications later.
- Data · Prisma and PostgreSQL. A reliable relational database for users, vehicles, and messages, with data access checked for errors as the code is written.
- Identity · Keycloak. Sign-in and permissions kept separate from the business logic, for the Buyer, Carbassador, and Administrator roles.
- Delivery · Docker, GitLab CI/CD, Harbor, Vault. Automated, versioned releases packaged as Docker images, with consistent development, QA, and production environments from day one.
- Hosting · Hetzner. Sized to the project’s budget and scale, without the overhead of a larger cloud setup.
How it was developed
Development started on June 23, 2025. The first tagged QA release followed about seven weeks later, and the client saw a working build every two weeks from then on. Version 1.0.0 shipped to production on November 21, 2025, and the platform has kept evolving in production since.
# 01 — Collaborative definition
The client brought the business concept. rinf.tech worked with them to define the application logic, user stories, and supporting features, including a way to report inappropriate interactions, before any code was written.
✓ Pre-agreed requirements ✓ Scoping with no fixed spec# 02 — Iterative development, reviewed every two weeks
From the first tagged QA release onward, working functionality was available for client review across separate development, QA, and production environments, so the client saw the product take shape every two weeks.
✓ Biweekly client demos ✓ Continuous functionality review# 03 — Verified identity before any conversation
A Carbassador registers a supported vehicle and passes an ownership check before becoming visible to a buyer. The check sits inside the matching logic, ahead of any moderation step. Chat is private and role-scoped, and each conversation can be reported: either side picks a reason and adds detail, and the conversation is locked while the report is in moderation.
✓ Ownership validated before visibility ✓ Moderated, role-scoped chat# 04 — Automated, reversible delivery
Changes are merged to the main branch, deployed to QA, validated, then promoted to production. Each release is versioned and packaged as a Docker image, a self-contained copy of the application, kept for redeployment. Its configuration is stored securely and restored with it, so a release can be rolled back without rebuilding from source. This has been in place from day one.
✓ Versioned releases, rollback-ready ✓ Consistent deployment across environmentsReal conversations, running in production
Production snapshot, August 2026.
Live in under five months.
Development started in June 2025, and version 1.0.0 shipped to production in November. The platform runs in Norway today.
Usage beyond sign-ups.
163 people had registered (100 buyers, 62 owners, and one administrator), and 75.9% of non-admin users had used the chat, including 77% of buyers and 72.6% of owners.
Conversations are happening.
93 buyer–owner connections, 467 messages, about five per connection. Buyer activity is transactional: people engage while researching a car and may go quiet after a purchase.
A business idea, taken to production
Carbassador shows that a business idea is enough to start. The client brought the concept. rinf.tech turned it into application logic, user stories, and a working platform. The trust mechanism at the center, which verifies the owner and then gates who becomes visible to whom, was a requirement from day one.
The engagement also left Carbassador with a foundation it owns: a Statement of Work, structured user stories, and project and technical documentation, all on widely used, non-proprietary technology. That reduces lock-in, and another skilled team could maintain the platform if needed.
A buyer comparing two cars can now put the question to an owner of the same model. The 467 messages across 93 connections show those conversations are happening, in production, in Norway, with a Swiss expansion planned.
- Industry
- Automotive / mobility marketplace
- Client
- Carbassador
- Engagement type
- End-to-end product development (idea to production, ongoing)
- Timeline
- Jun 2025 – Nov 2025 (dev start to v1.0.0)
- Team
- 12: 1 business analyst, 7 engineers, 4 QA
- Status
- Live in Norway, with a Swiss expansion planned