ExamGuardPro: Migrating to Production-Grade Web Infrastructure

Snapshot

• Client: ExamGuardPro
• Industry: EdTech / SaaS
• Timeline: 2 Weeks
• Stack: React, Node.js, Vite, TypeScript, Neon (PostgreSQL), OpenAI API

ExamGuardPro provides AI-driven proctoring solutions. They started as a rapid prototype on Replit but hit a wall when trying to scale. They needed a professional, production-ready environment to serve their growing user base.

The Problem

The client's codebase was trapped in a prototyping environment. Key challenges included:

1. Vendor Lock-in: The app relied on Replit-specific authentication (@replit/repl-auth), making it impossible to host elsewhere.
2. Build Failures: Attempting to deploy to standard hosts (Render/Vercel) resulted in vite: command not found errors due to proper dependency mismanagement in package.json.
3. Ephemeral Storage: They were using local SQLite files which vanished on every restart, unsuitable for production user data.

The Solution

Pureons engineered a full migration strategy to move the application to a resilient, scalable architecture.

1. Codebase Liberation & Clean-up

We moved the source code to GitHub and refactored the package.json.

• Dependencies Fixed: Moved vite and typescript from devDependencies to dependencies (or ensured the build command had access) to ensure Render's build pipeline could execute the build script.
• Strict Typing: Fixed implicit any types that were blocking the production build.

2. Database Migration (Neon PostgreSQL)

We replaced the local SQLite setup with Neon, a serverless PostgreSQL platform.

• Implemented connection pooling in db.ts to handle concurrent users.
• Migrated schema and seeded initial data.

3. CI/CD on Render

We set up a robust deployment pipeline on Render.

• Auto-Deploy: Commits to main trigger a zero-downtime deployment.
• Environment Management: Securely stored OpenAI API keys and Database URLs in Render's environment variable manager, removing all hardcoded secrets.

Implementation Details

Here is a glimpse of the technical work involved.

Fixing the Build Pipeline

Standardizing the npm scripts to work in a CI environment:

// package.json updates
"scripts": {
  "build": "tsc && vite build",
  "start": "vite preview --port $PORT",
  "dev": "vite"
}

Removing Replit Auth

We replaced the proprietary auth with a standard JWT-based auth system (or prepared for NextAuth integration).

// Removed @replit/repl-auth
// Added standard middleware for route protection
const checkAuth = (req, res, next) => {
  const token = req.headers.authorization?.split(' ')[1];
  if (!token) return res.status(401).json({ error: 'Unauthorized' });
  // Verify JWT...
  next();
};

Results

The migration transformed ExamGuardPro from a fragile prototype into a robust SaaS product.

• Reliable Builds: 100% success rate on deployments. No more "it works on my machine" issues.
• Persistent Data: User accounts and proctoring logs are now safely stored in Neon with daily backups.
• Scalability: The application can now handle traffic spikes without the underlying development container crashing.
• Developer Experience: The team now works with standard Git workflows, enabling collaboration and version control.

Conclusion

Prototyping tools are great for starting, but bad for scaling. Migrating to professional infrastructure is the most high-leverage move a growing SaaS can make.