blog: finalized Searchcraft use-case blog post.

Author: matijaSos

web/blog/2026-07-20-made-with-wasp-searchcraft.mdx

@@ -1,26 +1,25 @@
 ---
-title: "Made with Wasp: how Searchcraft built a full-stack SaaS for their Rust search engine"
+title: "Made with Wasp: how Searchcraft built a full-stack SaaS around their Rust search engine"
 authors: [matijasos]
 image: /img/searchcraft-vektron/searchcraft-hero.webp
 tags: [showcase, wasp, saas, rust, web dev]
 keywords: ["rust search engine", "algolia alternative", "elasticsearch alternative", "self-hosted search engine", "open source search engine alternative", "wasp framework production app", "full-stack react node prisma app", "saas dashboard framework", "open saas template", "search engine on raspberry pi", "build saas dashboard fast", "rust and react architecture", "multi-tenant saas example", "wasp use case"]
-description: "How Searchcraft, a Rust-based Algolia alternative, built Vektron - their full-stack user dashboard - with Wasp and the Open SaaS template."
-unlisted: true
+description: "How Searchcraft, a Rust-based Algolia alternative, built their full-stack customer dashboard with Wasp and the Open SaaS template."
 ---
 
 import { ImgWithCaption } from './components/ImgWithCaption';
 import { VideoWithCaption } from './components/VideoWithCaption';
 
 <ImgWithCaption
     source="img/searchcraft-vektron/searchcraft-hero.webp"
-    alt="Searchcraft - a Rust-based search engine, with Vektron, its Wasp-powered user dashboard"
+    alt="Searchcraft - a Rust-based search engine, with its Wasp-powered customer dashboard"
 />
 
 
 ## TL;DR
 
 - **[Searchcraft](https://searchcraft.io)** is a search engine written in Rust: an Algolia / Elasticsearch alternative that's light enough to run full-text search over all of English Wikipedia [on a single Raspberry Pi](https://www.youtube.com/watch?v=SjuPn6_yl2s).
-- **Vektron**, their full-stack user dashboard (auth, billing, analytics, index management), is built with **Wasp** and the [Open SaaS](https://opensaas.sh) template.
+- Their full-stack customer dashboard (auth, billing, analytics, index management) is built with **Wasp** and the [Open SaaS](https://opensaas.sh) template.
 - They could have built the SaaS layer themselves, but chose not to, so their engineering time stays in the Rust engine where they actually compete.
 - Wasp compiles to standard React + Node.js + Prisma, deployed on their own AWS and CI/CD. No lock-in, no restructuring.
 
@@ -40,7 +39,7 @@ And they're in production. Their first customer is a publisher running 22 local
 
 <ImgWithCaption
     source="img/searchcraft-vektron/vektron-documents-onboarding.webp"
-    alt="Vektron's onboarding screen: import documents from a feed URL, a file, or WordPress"
+    alt="The onboarding screen: import documents from a feed URL, a file, or WordPress"
     caption="The onboarding screen - Searchcraft's design is super cool!"
 />
 
@@ -50,44 +49,42 @@ They could have built it, but chose not to. The SaaS layer is a hundred solved p
 
 The answer came from inside the house: Don, the CTO, had been following Wasp. [Open SaaS](https://opensaas.sh), Wasp's open-source template, meant auth, payments, and an admin panel existed on day one, as code they own, not services they rent. And they evaluated it like engineers: everything Wasp generates is standard React, Node.js, and Prisma they could read, trust, and run themselves, no magic to open up. **It's their code**, and it compiles to one integrated stack built to keep holding together as the app grows.
 
-## What they built: Vektron
+## What they built: the full-stack customer dashboard
 
-Vektron is Searchcraft's control room, "a product within a product," where customers run everything from document ingestion to search tuning, team management, and analytics.
+The dashboard is Searchcraft's control room, "a product within a product," where customers run everything from document ingestion to search tuning, team management, and analytics.
 
-> **"Vektron is our Wasp app, it's the user portal. We just like to give things cool code names."**
-
-Three moments show what's actually running under the UI, because Vektron isn't a static admin panel, it's a full-stack app where Wasp is doing real work end to end:
+Three moments show what's actually running under the UI, because the dashboard isn't a static admin panel, it's a full-stack app where Wasp is doing real work end to end:
 
 <ImgWithCaption
     source="img/searchcraft-vektron/vektron-dashboard-analytics.webp"
-    alt="Vektron organization dashboard with live usage stats, conversion and retention scores"
+    alt="Organization dashboard with live usage stats, conversion and retention scores"
     caption="What's behind this screen: server-side queries turning raw search events into live stats and multi-tenant access control, all in one Wasp codebase."
 />
 
 <ImgWithCaption
     source="img/searchcraft-vektron/vektron-app-searches.webp"
-    alt="Vektron application view with the index registry and total searches chart"
+    alt="Application view with the index registry and total searches chart"
     caption="What's behind this screen: a multi-tenant index registry in Prisma, kept in sync with the Rust engine over one API, with search events rolled up into the time windows above. The chart is React; the plumbing is Wasp's type-safe operations."
 />
 
 <VideoWithCaption
     source="img/searchcraft-vektron/vektron-subscription-settings.mp4"
-    alt="Vektron organization settings with subscription plans and upgrades"
+    alt="Organization settings with subscription plans and upgrades"
     caption="What's behind this screen: subscription plans and upgrades, the billing machinery every SaaS needs and nobody wants to hand-roll, running in the same Wasp app and wired into the quotas from the first screen."
 />
 
 Around those three screens sits the rest of a real SaaS: an ingestion pipeline that infers the schema as it pulls documents in, crew management with roles, access keys as managed secrets, and a code-snippets page that takes a frontend dev from API key to working search box in minutes. Multi-tenant, role-based, revenue-carrying, and it looks the part. For a search company, the user portal *is* the brand.
 
 ## How it runs: Wasp next to Rust
 
-The shape is the interesting part. On one side, the Searchcraft engine and its supporting services (provisioning, ingestion), all Rust, all theirs. On the other, Vektron: a Wasp app (React + Node.js + Prisma) that talks to the engine over an API. Customer apps consume search through the SDKs and never know the portal exists.
+The shape is the interesting part. On one side, the Searchcraft engine and its supporting services (provisioning, ingestion), all Rust, all theirs. On the other, the customer dashboard: a Wasp app (React + Node.js + Prisma) that talks to the engine over an API. Customer apps consume search through the SDKs and never know the portal exists.
 
 Here's the architecture, drawn by the Searchcraft team:
 
 <ImgWithCaption
     source="img/searchcraft-vektron/searchcraft-architecture.webp"
-    alt="Architecture diagram: Vektron (Wasp app), Searchcraft Server (Rust), provisioning and ingestion services (Rust), SDKs, customer apps"
-    caption="Vektron, the Wasp app, handles users, configuration, and analytics; the Searchcraft engine and its Rust services do the search. One API connects them, and customer apps reach search through the SDKs."
+    alt="Architecture diagram: the customer dashboard (Wasp app), Searchcraft Server (Rust), provisioning and ingestion services (Rust), SDKs, customer apps"
+    caption="The dashboard, a Wasp app, handles users, configuration, and analytics; the Searchcraft engine and its Rust services do the search. One API connects them, and customer apps reach search through the SDKs."
 />
 
 **Two systems, one product, one API between them.**

web/src/components/WaspOutThere.tsx

@@ -39,6 +39,8 @@ interface RealApp {
   linkText: string;
   linkUrl: string;
   imageSrc: string;
+  storyText?: string;
+  storyUrl?: string;
 }
 
 const WaspOutThere = () => {
@@ -247,27 +249,39 @@ const FeaturedTestimonial = () => (
 );
 
 const ProjectCard = ({ project }: { project: RealApp }) => (
-  <Link
-    to={project.linkUrl}
-    className="block h-full overflow-hidden border border-wasp-black bg-wasp-white no-underline transition-shadow hover:shadow-md"
-  >
-    <img
-      src={project.imageSrc}
-      alt={project.name}
-      className="aspect-video w-full object-cover object-top"
-    />
-    <div className="p-4">
-      <h4 className="mb-1 font-mono text-base font-bold text-wasp-black">
-        {project.name}
-      </h4>
-      <p className="mb-3 text-sm leading-relaxed text-wasp-g6">
-        {project.description}
-      </p>
-      <span className="font-mono text-xs font-semibold text-wasp-black underline decoration-wasp-yellow decoration-2 underline-offset-2">
+  <div className="flex h-full flex-col overflow-hidden border border-wasp-black bg-wasp-white transition-shadow hover:shadow-md">
+    <Link to={project.linkUrl} className="block no-underline hover:no-underline">
+      <img
+        src={project.imageSrc}
+        alt={project.name}
+        className="aspect-video w-full object-cover object-top"
+      />
+      <div className="px-4 pb-3 pt-4">
+        <h4 className="mb-1 font-mono text-base font-bold text-wasp-black">
+          {project.name}
+        </h4>
+        <p className="text-sm leading-relaxed text-wasp-g6">
+          {project.description}
+        </p>
+      </div>
+    </Link>
+    <div className="mt-auto flex flex-wrap items-center gap-x-4 gap-y-1 px-4 pb-4">
+      <Link
+        to={project.linkUrl}
+        className="font-mono text-xs font-semibold text-wasp-black underline decoration-wasp-yellow decoration-2 underline-offset-2 hover:text-wasp-black hover:decoration-wasp-yellow-dark"
+      >
         {project.linkText}
-      </span>
+      </Link>
+      {project.storyUrl && (
+        <Link
+          to={project.storyUrl}
+          className="inline-flex items-center gap-1 bg-wasp-yellow px-1.5 py-0.5 font-mono text-xs font-semibold text-wasp-black no-underline transition-colors hover:bg-wasp-yellow-dark hover:text-wasp-black hover:no-underline"
+        >
+          {project.storyText ?? "read the story →"}
+        </Link>
+      )}
     </div>
-  </Link>
+  </div>
 );
 
 /* Bottom action zone of the example-app card: repo link + Demo + See the code. */
@@ -497,6 +511,8 @@ const realApps: RealApp[] = [
     linkText: "visit site →",
     linkUrl: "https://www.searchcraft.io/",
     imageSrc: "/img/lp/examples/searchcraft.webp",
+    storyText: "read the story →",
+    storyUrl: "/blog/2026/07/20/made-with-wasp-searchcraft",
   },
 ];