Version 1.0.0Web + App

Quick Start

From an empty server to a working AI SaaS and a Flutter app build.

Item: OmniGenix AI | Laravel Multi-Company Image and Video Content Creation SaaS With Flutter Mobile App  ·  Stack: Laravel 12 · PHP 8.2+ · MySQL 8 · Flutter (Dart 3.12+)

The Fast Path

Who does what? Steps 1, 3 and 5 below need someone with server access (upload, database, cron, worker) or a Flutter developer (the app). Everything else, including branding, AI keys, payment gateways, plans, mail and push, is done later in the browser in the admin panel without code. Full table: Start Here: Who Does What.

About 30 minutes on a VPS with SSH, PHP 8.2+ and MySQL 8. Every step links to the detailed guide.

1. Upload & install

Upload the web app, point the domain at public/, open the domain and finish the 4-step installer.

Open →
2. Cron & worker

One cron line and one Supervisor queue worker.

Open →
3. Connect services

Mail, one AI provider with models, one payment gateway with its webhook.

Open →
4. Build the app

Flutter with --dart-define=API_BASE_URL=https://your-domain.

Open →

What Is in the Package

FolderContents
Main_Files/WebSourceCodeThe Laravel 12 web app: SaaS admin, company workspace, landing page and blog, REST API v1, installer, migrations, seeders and the automated test suite
Main_Files/AppSourceCodeThe Flutter app (Android and iOS projects of one codebase), with its README.md
documentationThis documentation: Quick Start, Common Setup, Web Platform and Mobile App pages

Plain, readable PHP and Dart: no encoded files and no licence server. The download does not include vendor/: run composer install --no-dev --optimize-autoloader once (on your computer if your host has no SSH, then upload the vendor/ folder). The compiled CSS/JS ship in public/assets-compiled, so Node.js is not needed on the server.

1. Install the Web App

  1. Upload the files

    For example to /var/www/omnigenix, and point the domain’s document root at /var/www/omnigenix/public. Then run composer install --no-dev --optimize-autoloader in that folder (or upload a vendor/ folder built on your computer).

  2. Make folders writable

    chown -R www-data:www-data storage bootstrap/cache public/uploads and chmod -R 775 storage bootstrap/cache public/uploads.

  3. Create an empty database

    Charset utf8mb4, collation utf8mb4_unicode_ci, and a user with all privileges on it.

  4. Open your domain

    Every request redirects to /install: Requirements → Database and site → Install → Super Admin. The installer then locks itself (storage/app/installed).

CREATE DATABASE omnigenix CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
CREATE USER 'omnigenix'@'localhost' IDENTIFIED BY 'a-strong-password';
GRANT ALL PRIVILEGES ON omnigenix.* TO 'omnigenix'@'localhost';

Shared hosting with cPanel and no SSH? Follow cPanel Install (No SSH). Prefer the command line? See Command-Line Install. Never run plain php artisan db:seed on a live site; use --class=CoreSeeder.

2. First Run

  1. Sign in

    Open /login with the Super Admin you created in the installer.

  2. System Status

    Settings → System Status lists what still needs attention (cron, queue, mail).

  3. Brand it

    Settings → General Settings: site name, light and dark logo, favicon, currency, default language. Landing page & white-label: colours and hero text.

  4. Review the plans

    Free, Starter, Pro and Business are seeded. Edit prices, credits and limits; keep one active plan marked Default.

System Status warns until cron, queue and mail are set
System Status warns until cron, queue and mail are set

3. Cron & Queue

Add one cron entry for the web-server user (crontab -u www-data -e):

* * * * * cd /var/www/omnigenix && php artisan schedule:run >> /dev/null 2>&1

Set QUEUE_CONNECTION=database in .env and keep a worker running with Supervisor (full config in Common Setup). On shared hosting without a long-running process set QUEUE_VIA_SCHEDULER=true instead.

php /var/www/omnigenix/artisan queue:work --sleep=3 --tries=3 --timeout=960 --max-time=3600

4. AI & Payments

  1. Mail

    Settings → Mail Setting, then Send test mail.

  2. AI provider

    AI Management → AI Providers → Add (for example the openai driver with your own key) → Test connection. A fresh install has no working AI provider.

  3. AI models

    AI Management → AI Models → Add: one model per capability you sell (text, image, voice, transcription, embedding, video), each with a credit rate and provider cost.

  4. Payment gateway

    Billing & Payments → Payment Gateways: add Stripe, PayPal, Razorpay or Mollie with sandbox keys (or Manual for bank transfer) and register the webhook URL at the gateway, e.g. https://YOUR-DOMAIN/webhooks/stripe (all URLs and events: Payment Gateways).

  5. Test

    Register a test company, buy a plan and a top-up with a test card, and run one generation in each studio.

Details: AI Providers & Models, Payment Gateways & Webhooks.

5. Build the App

The Flutter app is in Main_Files/AppSourceCode. It needs only the URL of your web install:

flutter pub get
flutter gen-l10n
flutter run --dart-define=API_BASE_URL=https://your-domain.com

Before publishing, change the package/bundle id (com.omnigenix.app), the app name and icons, add your Firebase files for push, and sign the release build with your own keystore and Apple team. Everything is in Mobile App.

Login
Login
Home
Home
Studio
Studio

6. Go-Live Checklist

Required versus optional integrations are explained in Ready to Go Live?.

  • APP_ENV=production, APP_DEBUG=false, APP_URL is your public https:// URL.
  • HTTPS with a valid certificate; SESSION_SECURE_COOKIE=true.
  • Cron entry added; System Status shows the scheduler heartbeat.
  • Queue worker running (or QUEUE_VIA_SCHEDULER=true).
  • Mail test received; SPF/DKIM set for the sending domain.
  • At least one AI provider and models with credit rates; Test connection passes.
  • Payment gateway webhooks registered with live signing secrets after a sandbox test.
  • Demo accounts removed (*@acme.test, *@omnigenix.test) or installed without the sample company.
  • Strong, unique passwords on every admin account. Turn on two-factor authentication for each of them (user menu → Change Password → Two-factor authentication, see Web Platform → Security).
  • Public sign-up: leave it on, or switch it off in Settings → Signup & referrals → Allow new visitors to sign up (details).
  • Terms & Conditions and Privacy Policy pages edited for your business.
  • Nightly database and file backups copied off the server; APP_KEY stored safely.

Ongoing Costs

The item price covers the source code. Running a SaaS has ongoing costs (full table: Third-Party Services & Costs) that you pay to the providers directly: hosting and domain, e-mail delivery (SMTP), AI provider usage (OpenAI, Replicate, ElevenLabs, Runway, Luma, Kling), payment gateway fees, telephony minutes and numbers (Twilio/Plivo), optional S3-compatible storage, Firebase, social network developer apps, and Apple Developer / Google Play Console accounts for the app. You set your own prices and credit rates so that customers cover these costs; Usage & margin shows the margin per provider, model and company.