Launching a Custom AI Avatar Service on Shared Hosting

Shared hosting can support a serious first version of an AI avatar platform when the architecture respects its limits. PHP handles authentication and API requests, MySQL stores accounts and history, Stripe handles payment pages and card data, the AI provider performs model inference, and the browser performs speech recognition, speech synthesis, and local recording. The web server primarily coordinates these services and delivers optimized video files. FaceVI is designed around that division. This guide explains deployment, database upgrades, folders, configuration, background limitations, security, performance, monitoring, and the point at which a platform should move selected components to a VPS or managed service.

Understand what shared hosting should do

A shared Hostinger account is well suited to serving PHP pages, static assets, small API endpoints, and MySQL queries. It should not be expected to render AI video in real time, transcode large files continuously, or maintain long-lived WebSocket processes. FaceVI avoids those requirements. The five avatar states are prepared MP4 assets.

AI inference occurs through xAI. Payment occurs through Stripe Checkout. Voice recognition and playback occur in the browser. This keeps the PHP request short enough for typical hosting limits. The design is modular, so a dedicated text-to-speech or media service can be added later without replacing authentication, billing, or dashboards.

Upload the package in the correct location

The package contents belong directly in the existing public_html directory, not inside an additional nested public_html folder. The root should contain index.php, .htaccess, auth, app, admin, api, assets, includes, database, storage, uploads, and videos. Confirm that hidden files such as .htaccess were uploaded.

On Hostinger, select a supported PHP version and enable PDO MySQL, cURL, JSON, OpenSSL, fileinfo, and DOM. The domain should point to the correct document root and use an SSL certificate. After upload, create includes/config.php from the example and enter the full database name and username shown by hPanel, including the account prefix.

Create and protect configuration

The configuration file contains the site URL, database credentials, encryption key, AI key, Stripe values, mail settings, and OAuth values. Generate a long random encryption key before storing encrypted admin settings. The .htaccess rules block direct access to config.php, SQL, logs, and documentation, but correct file permissions remain important.

Do not place keys in JavaScript, screenshots, support tickets, or source-control repositories. The admin settings page can store secrets encrypted with the application key, while config values remain a fallback. Changing the encryption key after secrets have been stored makes those encrypted values unreadable, so preserve it securely.

Install or upgrade without losing data

A fresh installation runs install.php once to create tables, seed characters, add knowledge articles, and create the administrator. An existing working site should use the versioned upgrade script instead of deleting the database. The FaceVI version-two upgrade checks for columns before adding them, creates the custom-order and blog tables, inserts content without replacing existing rows, and writes a lock file.

Back up the database and public_html before any upgrade. After success, delete the public upgrade script and keep the lock. Database changes should be idempotent where possible so a timeout can be safely diagnosed and retried rather than forcing a full reinstall.

Configure Stripe in test mode first

Create one-time Prices for five and ten minutes, a recurring Price for the monthly plan, and a recurring $199 Price for the custom-character service. Enter Price IDs, the secret key, and webhook secret. Register the FaceVI webhook endpoint and subscribe to checkout completion, invoice payment, and subscription updates.

Test with Stripe test mode. Confirm that a completed credit purchase adds time once, a repeated webhook does not add it twice, a subscription appears in the database, and a custom order changes from awaiting payment to pending. Payment pages should never collect card numbers directly in FaceVI forms. Stripe Checkout reduces compliance scope and provides a familiar payment experience.

Set up transactional email

Account verification, password reset, low-credit alerts, auto-recharge notices, custom-order pending confirmations, and ready notifications require reliable email. PHP mail may work on shared hosting, but authenticated SMTP is usually more predictable. Configure a domain mailbox, SPF, DKIM, and DMARC according to the mail provider.

Use a from address on the FaceVI domain and a monitored reply address. Test delivery to several providers and check spam folders. Email failures should not roll back a successful payment or order approval; they should be logged so the administrator can resend or contact the customer manually.

Manage the custom-character folder workflow

Each paid order has an account-specific folder such as videos/custom/USERID-username/order-ORDERID. The administrator uploads idle.mp4, listening.mp4, thinking.mp4, speaking.mp4, and gesture.mp4 using the dashboard or Hostinger File Manager. Reference images are stored in uploads/custom under a parallel account path.

Upload folders block executable script extensions. Because shared hosting can impose upload limits, File Manager is often the best way to place large final videos. The admin page displays the expected folder and checks that all five files exist before approval. This operational convention is simple, auditable, and easy to back up.

Optimize video delivery

Compress video before upload. Use a widely supported H.264 MP4 profile, remove unnecessary audio, match dimensions to the displayed aspect ratio, and use a moderate frame rate. A visually clean 720p clip can look better and load faster than an oversized 4K export. Keep loops short and consistent.

Configure cache headers for MP4 files and avoid loading all state videos for every character on the landing page. Character cards can show idle clips with metadata preload and lazy playback. The chat page needs the current state immediately and can allow browser caching to make later switches faster. Monitor total storage because five clips multiplied by many custom accounts grows steadily.

Respect PHP limits

Check upload_max_filesize, post_max_size, max_execution_time, memory_limit, and max_input_vars in hPanel. The application can validate a large MP4, but PHP cannot receive a file larger than its server limit. Use File Manager for very large assets. AI requests need a timeout long enough for the provider but should not remain open indefinitely.

Avoid loading enormous conversation histories; send a recent window. Database indexes on user, status, date, and Stripe identifiers prevent dashboards from slowing as records grow. Paginate admin tables when activity becomes large. Shared hosting performs well when each request has a bounded amount of work.

Monitor errors and usage

The admin dashboard should show users, revenue, messages, usage time, pending orders, production orders, and custom monthly revenue. Error logs capture safe messages and context. Activity logs track login and administrative changes. Stripe events preserve payment processing history.

Review logs after deployment and after changing keys or webhooks. A sudden increase in AI errors may indicate an API key, model name, quota, or provider issue. A rise in failed logins may justify stricter rate limits. Usage reports help compare revenue with AI costs and identify popular characters. Monitoring is part of the product, not an afterthought.

Back up files and database

Use Hostinger backups or create scheduled exports appropriate to the plan. The database contains accounts, messages, orders, prompts, and billing references. The file system contains avatar videos, reference images, blog banners, and configuration. A database backup without the custom video folders cannot fully restore the service.

A file backup without the database loses ownership and order status. Protect backups because they may contain personal and commercial information. Test a restoration process on a separate environment when possible. Keep the encryption key with the backup through a secure method, since encrypted settings depend on it.

Know when to add a VPS or managed service

Move a component when a specific limit appears, not simply because the platform is called AI. A VPS may be appropriate for real-time streaming, custom speech services, video generation, transcoding queues, WebSockets, or high traffic. Object storage and a CDN may be appropriate when custom video volume grows.

A managed email service can improve deliverability. A background queue can handle production notifications and retries. The PHP/MySQL application can remain the account and business system while media or AI components move. A modular architecture protects the investment already made in the dashboard, payments, and user experience.

Launch-day checklist

Back up the database and files. Confirm the production URL and SSL. Test registration, verification, login, password reset, a typed chat, a voice chat, zero credits, a test Stripe purchase, a custom subscription, the webhook, order status, admin upload, approval, and ready email. Test on mobile data as well as Wi-Fi.

Delete install and upgrade scripts. Change the default admin password. Review error logs after the first real sessions. Keep Stripe in test mode until every state is verified, then switch all related keys and Price IDs together.

The first month of operations

Review usage and errors daily at first. Answer support tickets quickly because early questions reveal unclear interface text. Track AI cost per paid minute. Watch storage growth from custom videos. Verify backups.

Improve the most-viewed knowledge articles. Record why custom orders require clarification and update the form examples. Review failed payments and cancellation handling. Avoid adding many features before the core purchase, conversation, and production flows are stable. A dependable service with a small feature set creates a stronger foundation than a broad platform with unresolved operational gaps.

Security hardening after installation

Remove install and upgrade scripts, change the default administrator password, and require a unique strong password. Verify that directory indexes are disabled and that configuration, SQL, logs, and database folders cannot be opened directly. Test that uploaded PHP files cannot execute inside upload directories. Keep PHP and dependencies current. Restrict administrator access and avoid using the admin account for ordinary browsing. Review session cookie settings under HTTPS. Confirm that error pages do not display stack traces in production. Rotate a secret immediately if it appears in a screenshot, support ticket, repository, or client-side code.

Capacity planning with simple measurements

Track daily active users, AI requests, average response time, charged seconds, Stripe revenue, storage per custom order, database size, and error rate. Estimate how many conversations fit within provider and hosting limits. Video bandwidth may become a larger expense than PHP execution, especially when many character cards autoplay. Use caching and consider a CDN when traffic grows. Identify the first constraint with measurements rather than assumptions. A shared-hosting service can scale farther than expected when static media is optimized and external providers handle expensive computation, but it needs an explicit plan for storage, bandwidth, and support workload.

Operational roles and customer expectations

Even a small service needs responsibility for payments, support, production, content, and technical incidents. Define who reviews a custom order, who uploads videos, who confirms approval, and who responds when a payment succeeds but an email fails. Set business hours and communicate the twenty-four-hour production target accurately. Create reusable support replies without hiding individual circumstances. Keep a manual path for correcting an order when automation fails. The platform reduces administrative work, but customer confidence depends on timely human follow-through when a request reaches the pending queue.

Practical next steps

Begin with one controlled test and document the result. Use a test account, a non-sensitive question, and a clear expected outcome. Review the visible text, spoken delivery, state transitions, account records, and any email or payment event involved. Record what worked, what was confusing, and which setting controls the behavior. Make one change at a time and repeat the test. This disciplined approach is useful for customers learning the product and for administrators operating it. It prevents an attractive interface from hiding unresolved workflow problems and creates a reliable path from demonstration to daily use.

Keep the user’s goal at the center. Features such as animation, voice, billing, recording, search, and custom media should reduce effort or improve clarity. When a feature adds complexity without helping the next action, simplify it. Review support questions as evidence about the interface. Update examples, knowledge articles, and form labels before adding more controls. A production platform becomes easier to trust when every state has a meaning, every payment has a status, every private asset has an owner, and every error has a recovery step.

Conclusion

A production-minded AI avatar service can begin on shared hosting by assigning each task to the right place. Hostinger serves PHP, MySQL, and static assets. Stripe manages checkout. xAI generates responses. The browser manages voice and local recording. Prepared MP4 states create the visual presence. Secure configuration, versioned upgrades, predictable folders, optimized video, email, webhooks, logs, and backups turn that architecture into an operable business. As demand grows, individual components can move to specialized infrastructure without discarding the core FaceVI platform.

Key terms and concepts

Deployment terms include document root, the public web folder; environment configuration, server-specific settings; migration, a controlled database change; webhook secret, the key used to verify Stripe events; cache control, instructions that let browsers reuse assets; MIME type, a file’s media format; and observability, the logs and metrics used to understand operation. Knowing these terms makes troubleshooting faster.