Freelance 2020-2022
My own software business (2020-2022)
Paid software I designed, built and sold on my own: online services, themes and payments
I ran a small software business on my own: two full online services, two paid themes, and the license and payment tools they shared.
- Role
- Owner and only developer
- Years
- 2020-2022
- Scope
- 2 services, 2 themes, shared tools
- Made for
- Sellers, web hosts, PHP developers
01 The problem
Small online sellers, web hosting companies and film site owners wanted a ready site they could run without code. PHP developers wanted to protect the code they sell. I built a paid, ready product for each group.
02 Result
- Sold as paid products. A license check let only paying buyers use the Daal theme.
- Paid code jobs ran on their own, from upload and payment to download.
- Bought or renewed internet accounts were created or extended in the billing system automatically.
03 What I built
- 01
Digital goods store
A complete store a seller installs with one setup command: customer area, admins with roles, help desk, coupons, tax and two languages.
- 02
Code protection service
Customers upload PHP code, choose where and until when it may run, pay from a wallet and download it. SMS phone checks and tickets included.
- 03
Film site theme (Daal)
Owners add a film by its IMDb ID. The theme fills in title, cast, rating, plot and poster, and translates parts into Persian.
- 04
Web hosting theme (Hoster)
Hosting companies manage plans, prices and offers from the admin panel. A smart search helps buyers find the right plan.
- 05
Shared business tools
A license server that creates, checks and cancels licenses for my products, and a self-hosted gateway for TRX and USDT payments.
- 06
Add-ons for developers
A public email builder for Persian and English, and a ready admin panel with its own login, for other developers.
04 Risks I handled
- Risk 01
Renewals in a billing system
The internet providers' billing system offered no connection for other software. The store signs in to its admin pages like a person, creates accounts, and adds time to active ones or restarts ended ones.
- Risk 02
Slow work off the website
Protecting code is slow and needs special software. The website puts each paid job in a queue, sends it to a separate encoding server, and tells the customer when it is ready.
- Risk 03
Four gateways, one checkout
Each of the four payment gateways works in its own way. One shared checkout runs the common steps, and each gateway adds only its own small part.
05 Stack
- PHP
- Laravel
- WordPress
- MySQL
- Payment gateways
- Job queues
- Tron (TRX, USDT)
06 How it works
- 01Build each product as a ready package, theme or online service
- 02Add an install step, online payments and license checks
- 03Give owners an admin panel, so they need no code
- 04Ship updates, such as a newer Laravel version for the store
Get in touch.
Hiring an engineering lead, or building a platform or AI agents? Tell me about it.