Full-Stack + DevOps Migration to OJASVIX

Senior Full-Stack + DevOps Engineer — Replit Exit & Web/Mobile Deployment

Project

I have a fully functional SaaS product called Pedagogical AI Studio, developed using Replit Agent.

The product includes:

* Web application
* Backend/API
* PostgreSQL database
* AI functionality
* Authentication
* File/storage functionality
* Payments
* iOS/mobile application
* Android/mobile application

I want to move the entire production environment away from Replit to infrastructure controlled by my company, OJASVIX.

I also want the mobile applications prepared and published on:

* Apple App Store
* Google Play Store

The application is already built and functional. This is primarily a migration, productionization, deployment and publishing project, not a rebuild.

⸻

Target Architecture

I want to continue using Replit + Replit Agent for development.

Desired workflow:

Replit + Replit Agent
↓
Development / Testing
↓
GitHub
↓
Automated Tests / Build
↓
OJASVIX Production

Replit should remain useful for:

* Fixing bugs
* Developing new features
* Testing changes
* Maintaining the application

However, production must not depend on Replit.

The production environment should be fully controlled by OJASVIX.

⸻

1. COMPLETE REPLIT AUDIT

Before migration, audit the entire application and identify:

* Replit-specific dependencies
* Replit database dependencies
* Replit storage dependencies
* Environment variables
* Secrets
* AI integrations
* External APIs
* Authentication
* Payment integrations
* Email services
* File uploads
* Background jobs
* Scheduled jobs
* Webhooks
* Mobile API dependencies
* Build/deployment dependencies

Provide a written migration plan before making major changes.

⸻

2. WEB APPLICATION

Move the production web application from Replit to OJASVIX-controlled infrastructure.

Requirements:

* Dockerized production environment
* HTTPS/SSL
* Custom domain
* Cloudflare or equivalent
* Secure environment variables
* Logging
* Health checks
* Monitoring
* Rollback capability

Existing functionality must remain intact.

⸻

3. BACKEND/API

Move the backend/API completely out of Replit.

Both the web and mobile applications must use the new OJASVIX production API.

Configure:

* HTTPS
* Authentication
* CORS
* Rate limiting
* Secure secrets
* Logging
* Health endpoint
* Error handling
* Monitoring

⸻

4. DATABASE MIGRATION

Migrate the existing PostgreSQL database from Replit to independent production infrastructure.

Requirements:

* Preserve all existing data
* Preserve relationships
* Preserve users
* Preserve application state
* Verify migration
* Automated backups
* Restore procedure
* Separate development and production databases

Development must never use the production database.

⸻

5. STORAGE MIGRATION

If Replit storage is currently used, migrate production files/data to independent storage.

Existing uploaded files must remain accessible after migration.

⸻

6. AI

The application uses AI functionality.

Production AI configuration should be independent of Replit where possible.

Create an AI abstraction layer where practical so that AI providers can be changed in the future without rewriting the application.

Production AI credentials must be securely stored.

⸻

7. MOBILE APPLICATION

Connect the existing mobile application to the new OJASVIX production API.

Test all major functionality, including:

* Login/registration
* Authentication
* API communication
* AI features
* File uploads
* User profiles
* Payments
* Notifications, if applicable
* Other existing functionality

Both iOS and Android builds must use the production environment.

⸻

8. APPLE APP STORE

Prepare and publish the iOS application to the Apple App Store.

This includes:

* Production build
* Bundle identifier
* Signing
* Certificates/provisioning
* App Store Connect configuration
* Store listing
* Screenshots
* Privacy information
* Required declarations
* TestFlight testing
* Production submission
* Handling technical rejection issues

The Apple Developer account must be owned by OJASVIX.

The freelancer will receive appropriate access but will not own the account.

⸻

9. GOOGLE PLAY

Prepare and publish the Android application to Google Play.

This includes:

* Production build
* Package name
* Signing
* Play Console configuration
* Store listing
* Screenshots
* Privacy information
* Required declarations
* Internal/closed testing if required
* Production submission
* Handling technical rejection issues

The Google Play Console account must be owned by OJASVIX.

⸻

10. CI/CD

Set up a reliable deployment pipeline.

Preferred workflow:

Replit
↓
GitHub
↓
Automated Tests
↓
Build
↓
Production Deployment

I should not have to manually copy files from Replit to production.

Production must support rollback to a previous working version.

⸻

11. DEVELOPMENT VS PRODUCTION

Completely separate:

Development

* Replit
* Development database
* Development storage
* Development API keys
* Test data

Production

* OJASVIX infrastructure
* Production database
* Production storage
* Production API keys
* Real customer data

Production credentials must never be stored in the development environment.

⸻

12. MONITORING

Set up basic monitoring for:

* Website uptime
* API uptime
* Server health
* CPU
* RAM
* Disk
* Database
* Application errors
* Backups
* Deployment status

I am not a developer, so the final system should be reasonably understandable to a non-technical owner.

⸻

13. SECURITY

Review and harden:

* Authentication
* API security
* CORS
* Rate limiting
* HTTPS
* Firewall
* Open ports
* Database access
* Secrets
* File permissions
* Storage permissions
* Backups
* Environment variables

PostgreSQL should not be publicly exposed unless absolutely required.

⸻

14. BACKUPS & DISASTER RECOVERY

Configure:

* Automated database backups
* Storage backup strategy
* Restore procedure
* Production rollback
* Recovery documentation

The platform must be recoverable if a deployment or server fails.

⸻

15. OJASVIX ACCOUNT OWNERSHIP

All critical accounts must be owned by OJASVIX, including:

* Domain
* GitHub
* Cloud/VPS infrastructure
* Database
* Storage
* Apple Developer
* App Store Connect
* Google Play Console
* Payment provider
* AI providers
* Monitoring
* Email services

The freelancer must not create critical production infrastructure under personal accounts.

⸻

16. DO NOT REBUILD THE PRODUCT

The product is already developed and functional.

I am not hiring someone to rebuild it from scratch.

The goal is:

Existing Replit application

→ Independent OJASVIX production infrastructure

→ Production web application

→ Production iOS application

→ Production Android application

→ App Store + Google Play

while preserving existing functionality.

Do not rewrite the application unnecessarily.

⸻

Deliverables

At completion I expect:

Web

* Production web application
* Custom domain
* HTTPS
* Production backend
* Production database
* Production storage

Mobile

* Production iOS application
* Production Android application
* App Store submission/release
* Google Play submission/release

Infrastructure

* Dockerized production
* GitHub integration
* CI/CD
* Monitoring
* Logging
* Backups
* Rollback

Migration

* Database migrated
* Storage migrated
* Replit production dependencies removed
* Production secrets migrated
* Production API independent of Replit

Documentation

Provide documentation covering:

1. Architecture
2. Deployment
3. Rollback
4. Database backup/restore
5. Environment variables
6. Server management
7. Mobile release process
8. App Store management
9. Google Play management
10. External services/dependencies

⸻

Required Experience

Strong experience with:

* Replit / Replit Agent
* Docker
* Linux
* PostgreSQL
* GitHub
* CI/CD
* VPS/cloud infrastructure
* SaaS production deployment
* REST APIs
* React/Next.js or relevant frontend
* Node.js/Python or relevant backend
* iOS deployment
* Android deployment
* App Store Connect
* Google Play Console

Experience migrating existing Replit applications is strongly preferred.

⸻

Application Requirements

Please provide:

1. Examples of similar projects
2. Replit migration experience
3. iOS + Android publishing experience
4. Proposed architecture
5. Recommended infrastructure/provider
6. Estimated timeline
7. Fixed-price or milestone quote
8. Required access
9. Database migration approach
10. Storage migration approach
11. How Replit development will remain compatible with production
12. How production-only failures will be diagnosed
13. Rollback strategy
14. Security approach

Please do not send a generic proposal.

I am looking for someone who can take an existing working Replit application and turn it into a properly managed, independent production SaaS platform under OJASVIX.