OSI Affiliate is a platform for running your own affiliate program, built by Omnistar Interactive — a US-based company that released the first version back in 2001. The name is simply an abbreviation of the developer's name. Over two decades, the product grew from a basic tracking script into a full-featured system with an affiliate portal, built-in analytics, payout management, and integrations with dozens of popular platforms.
The core premise is straightforward: OSI Affiliate lets businesses run a white-label affiliate program without depending on third-party affiliate networks. You don't pay network commissions, you set your own terms, and your data stays on your server.
Editions and Licensing
OSI Affiliate comes in a few deployment options.
Cloud (SaaS) — Omnistar hosts the platform on their infrastructure. No server management required. Plans run from $47/month for the basic tier to $97/month for the professional plan with more affiliates and extended features.
Self-hosted — the platform installs on your own server. One-time license purchase, full control over the data. This is the primary scenario for VPS deployments — your server, your rules.
Enterprise — for larger organizations with customization requirements and dedicated support. Pricing is negotiated individually.
All editions include the core functionality: click and conversion tracking, affiliate portal, commission management, and reporting. The differences are in affiliate count limits, advanced integrations, and support tiers.
Architecture and Technical Stack
OSI Affiliate runs on a standard PHP/MySQL stack. No exotic dependencies — just a conventional LAMP environment available on any Linux VPS.
Server-side:
- PHP 7.4+ (PHP 8.0-8.2 recommended)
- MySQL 5.7+ or MariaDB 10.4+
- Apache 2.4 or Nginx
- SSL required (HTTPS throughout)
- Cron for background tasks (transaction processing, notification delivery)
Client-side:
- Responsive affiliate portal interface
- Web-based admin panel
- REST API for external system integrations
The platform doesn't require Node.js, Python, or any additional runtimes — just PHP and MySQL. That keeps server requirements low and maintenance straightforward.
Hosting Requirements
Resource demands are modest. OSI Affiliate isn't a high-traffic application under normal conditions.
Minimum configuration for a small program (up to 50 affiliates):
- 1 vCPU / 2 GB RAM / 20 GB SSD
- PHP 7.4+, MySQL 5.7+
Recommended configuration for an active program (50-300 affiliates):
- 2 vCPU / 4 GB RAM / 40 GB NVMe
- PHP 8.1+, MySQL 8.0+
- Nginx + PHP-FPM
Performance configuration for high traffic (300+ affiliates, heavy click volume):
- 4 vCPU / 8 GB RAM / 80 GB NVMe
- Separate MySQL server
- Redis for session and query caching
Operating system: Ubuntu 22.04 LTS or Debian 12 are the most thoroughly tested options.
Installing OSI Affiliate on a VPS
This assumes Apache/Nginx, PHP, and MySQL are already configured. If not, start with a LAMP stack setup.
Prepare the server
Update the system and install dependencies:
apt update && apt upgrade -y
apt install -y apache2 php php-mysql php-curl php-gd php-mbstring php-xml mysql-server unzip
Start MySQL and run the initial security configuration:
systemctl enable --now mysql
mysql_secure_installation
Create the database
mysql -u root -p
In the MySQL console:
CREATE DATABASE osi_affiliate CHARACTER SET utf8mb4 COLLATE utf8mb4_unicode_ci;
CREATE USER 'osi_user'@'localhost' IDENTIFIED BY 'strong-password';
GRANT ALL PRIVILEGES ON osi_affiliate.* TO 'osi_user'@'localhost';
FLUSH PRIVILEGES;
EXIT;
Upload and extract files
After purchasing the license you receive an archive with the platform files. Upload it to the server and extract into the web root:
cd /var/www/html
unzip osi-affiliate-latest.zip -d affiliate
chown -R www-dаta:www-data /var/www/html/affiliate
chmod -R 755 /var/www/html/affiliate
Directories for uploaded files need write permissions:
chmod 777 /var/www/html/affiliate/uploads
chmod 777 /var/www/html/affiliate/cache
Configure Apache
Create a virtual host:
nano /etc/apache2/sites-available/affiliate.conf
<VirtualHost *:80>
ServerName affiliate.your-domain.com
DocumentRoot /var/www/html/affiliate
<Directory /var/www/html/affiliate>
Options -Indexes +FollowSymLinks
AllowOverride All
Require all granted
</Directory>
ErrorLog ${APACHE_LOG_DIR}/affiliate-error.log
CustomLog ${APACHE_LOG_DIR}/affiliate-access.log combined
</VirtualHost>
a2ensite affiliate
a2enmod rewrite
systemctl restart apache2
Web installer
Open http://affiliate.your-domain.com/install in a browser.
The installer walks through several steps:
Step 1: Requirements check — the system verifies PHP versions, required extensions, and file permissions. Green checkmarks mean proceed; red means fix on the server before continuing.
Step 2: Database connection — enter the host (localhost), database name (osi_affiliate), username, and password. The system creates the full table structure.
Step 3: Site configuration — your store or service URL, the affiliate program URL, and admin email address.
Step 4: Admin account — name, email, and password for the management panel.
Step 5: Finish — the installer removes the /install directory for security and displays links to the admin panel and affiliate portal.
Set up SSL
A production installation must run over HTTPS throughout:
apt install certbot python3-certbot-apache
certbot --apache -d affiliate.your-domain.com
Certbot automatically configures the HTTP-to-HTTPS redirect and sets up certificate renewal.
Configure cron
OSI Affiliate relies on background tasks for transaction processing and notifications. Add to crontab:
crontab -e
*/5 * * * * wget -q -O /dev/null https://affiliate.your-domain.com/cron/run.php
Running every five minutes covers the needs of most affiliate programs.
Key Features
Conversion Tracking
OSI Affiliate supports several tracking methods simultaneously, reducing conversion loss when cookies are blocked or cleared.
Cookie tracking is the baseline. A visitor clicks an affiliate link, a cookie is set in their browser, and when they purchase, the system reads the cookie and attributes the sale. You configure the cookie lifetime — 30, 60, 90 days, or longer depending on your sales cycle.
Coupon tracking assigns unique promo codes to affiliates. The customer enters the code at checkout and the sale attributes without any browser dependency. This matters for audiences that actively clear history or switch between devices.
Pixel tracking places a pixel on the order confirmation page. When the page loads, the pixel fires and sends conversion data to OSI Affiliate, running alongside cookie tracking as a backup layer.
Server-to-server postback (S2S) passes conversion data directly between servers, bypassing the browser entirely. The most reliable method — ad blockers and privacy tools have no effect.
Commission Management
Flexibility in commission configuration is one of OSI Affiliate's genuine strengths.
Different commission tiers for different partner categories: new affiliates get 10%, established partners with volume get 20%, VIP partners on exclusive terms get 30%.
Per-product or per-category commission rules: pay more for flagship products, standard rates for commodity items.
Recurring commissions: for subscription businesses, affiliates earn a percentage of each subsequent payment from the customers they referred — either indefinitely or for a defined period.
Bonus programs: additional payouts when partners hit volume thresholds. Bring in 50 customers in a quarter and earn a $500 bonus on top of standard commissions.
Affiliate Portal
Every affiliate gets access to a branded personal dashboard. Inside:
- Personal affiliate links and promo codes
- Performance stats: clicks, leads, sales, conversion rate
- Earnings history and payout status
- Marketing assets: banners, text links, email templates
- Documents: agreement, promotional guidelines
The portal is configured to match your brand colors and style. Affiliates see your domain and logo, not OSI's interface.
Payout Management
OSI Affiliate automates most of the payout workflow.
A minimum payout threshold reduces transaction overhead — affiliates only receive payment once they've accumulated a set amount, say $50.
A holding period sits between a conversion being recorded and the commission becoming payable. Setting 30 days covers most return windows: the conversion shows as "Pending" for that period, then moves to "Approved" and becomes eligible for payment.
Bulk PayPal payouts let you pay all affiliates simultaneously from a single action. CSV export handles bank transfer payouts or any other payment method.
Integrations
Ready-made connectors to popular platforms are one of OSI Affiliate's main advantages over building something custom.
E-commerce platforms: WooCommerce, Shopify, Magento, PrestaShop, OpenCart, BigCommerce, Volusion, 3dcart. Integration means order data flows into OSI Affiliate automatically, no custom development needed.
Payment systems: PayPal, Stripe, Authorize.Net, Braintree. Transactions from payment processors automatically match against conversions in the affiliate program.
CMS and site builders: WordPress, Wix, Squarespace, Weebly. A dedicated WordPress plugin reduces integration to a few clicks.
Email marketing: Mailchimp, Constant Contact, AWeber. New affiliates automatically land in the right mailing lists.
API: REST API for custom integrations with any system not covered by ready-made connectors.
Use Case Examples
Case 1: Home goods e-commerce store
WooCommerce store, 2,000 SKUs, average order value $80. The business wants to bring in home décor bloggers on a CPS (Cost Per Sale) basis.
OSI Affiliate implementation:
- WooCommerce integration via the dedicated plugin — order data syncs automatically
- 8% commission on order total, $30 minimum payout threshold
- 21-day holding period to account for the return policy
- Product photos, descriptions, and banners in multiple formats provided to affiliates
- Promo codes for bloggers to enable coupon tracking where cookies don't stick
- Monthly PayPal payouts
Six months in: 45 active affiliates, 12% of revenue coming through the affiliate channel.
Case 2: SaaS analytics service for small business
Subscription service, plans from $29/month. The company wants a referral program for existing customers and a separate affiliate program for agencies.
OSI Affiliate implementation:
- Two partner types: customers (20% of first payment) and agencies (30% of first payment + 10% recurring on each subsequent charge)
- Stripe integration via webhook — subscriptions tracked automatically
- Customers find their referral link inside the SaaS dashboard via the OSI API
- Agencies get a separate onboarding flow and extended marketing asset library
- $100 minimum payout, paid quarterly
Case 3: Professional online learning platform
Programming and design courses, average course price $300. The school wants to build a network of community curators who promote courses in their own channels.
OSI Affiliate implementation:
- Two-tier program: curators earn 25% on each of their students' purchases, plus 5% when a student they referred becomes a curator themselves
- Coupon tracking as the primary method — curators work in Telegram and Instagram where cookies don't carry across sessions
- Personalized landing page with a unique URL for each curator
- Automatic notification on every sale
- Monthly payouts, $50 minimum threshold
When OSI Affiliate Is the Right Choice
OSI Affiliate fits well in a few specific situations.
If you need to launch a program quickly without deep technical expertise — the web installer, ready-made integrations, and straightforward interface keep the barrier low.
If your program is small to mid-sized (under 300 affiliates) and doesn't require exotic functionality — OSI Affiliate covers the standard use cases without the cost of larger platforms.
If you want a one-time payment rather than ongoing subscription fees — the self-hosted license pays for itself over time compared to monthly SaaS alternatives.
If your store or service runs on one of the mainstream platforms — there's almost certainly a ready connector, and setup takes hours rather than days.
When OSI Affiliate Isn't the Best Fit
For programs with complex multi-tier structures, non-standard attribution logic, or highly customized commission rules, Post Affiliate Pro or a purpose-built solution offers more flexibility.
For very large programs — thousands of affiliates, millions of daily clicks — OSI Affiliate wasn't designed for that scale. You'd be looking at architectural rework or a move to enterprise software.
If your site runs on a custom in-house platform, integration requires API development, which removes the main advantage of ready-made connectors.
Alternatives
Post Affiliate Pro — richer feature set, more integrations, higher cost. The natural next step when OSI Affiliate's functionality runs out.
iDevAffiliate — comparable positioning, also self-hosted with a one-time purchase. Slightly simpler setup, somewhat thinner feature set.
AffiliateWP — the obvious choice if your site runs on WordPress. Doesn't work outside of WordPress.
Tapfiliate / Refersion — cloud alternatives that don't require a server. More expensive long-term, but no infrastructure to maintain.
LeadDyno — cloud solution oriented toward Shopify merchants. Simpler than OSI to configure, less flexible in the commission structure.
Security and Maintenance
A few things need ongoing attention after launch.
Install OSI Affiliate updates promptly — security patches come through them. Subscribe to release notifications from Omnistar.
Regular database backups. An affiliate program is financial data you can't afford to lose:
mysqldump -u osi_user -p osi_affiliate > /backup/osi-affiliate-$(date +%Y%m%d).sql
Monitor for traffic anomalies. A sudden spike in clicks from one affiliate without a corresponding uptick in conversions is a signal worth investigating. OSI Affiliate includes basic fraud detection tools; supplement them with manual review.
Remove the install directory after the initial setup:
rm -rf /var/www/html/affiliate/install
Conclusion
OSI Affiliate covers the needs of small to mid-sized affiliate programs without the cost of larger enterprise platforms. Ready-made integrations with mainstream e-commerce and payment platforms, a straightforward interface, and a self-hosted model with a one-time license fee make it a practical starting point.
For programs that outgrow it — complex attribution rules, thousands of affiliates, non-standard structures — Post Affiliate Pro or a custom build makes more sense. For WordPress-native sites, AffiliateWP integrates more cleanly.
A VPS on THE.Hosting with 2 vCPU / 4 GB RAM / 40 GB NVMe handles OSI Affiliate comfortably for programs up to 300 affiliates. NVMe storage keeps MySQL responsive.