How FileKicker Works
1. To begin, you (the shareware developer) create a new account on FileKicker. FileKicker then generates and
emails a secure password to you. Log into FileKicker the first time with your new password, and then change it to anything you wish.
2. Once you're logged in, you provide FileKicker with a short descriptive name of your file as well as its origin URL.
3. FileKicker then checks for three things: 1) that your file exists, 2) that your file meets FileKicker's size
requirements, and 3) that your file can be cached by FileKicker's download servers.
4. After confirming those three things, FileKicker provides a new "kicked" URL that you, the shareware developer,
distribute to your customer base.
5. When an intrigued user clicks a "kicked" URL, FileKicker instantly determines if the referring URL is one of your
blocked sites. FileKicker then double-checks to ensure the referring URL hasn't expired.
6. Next, FileKicker checks to see if it has received a request from that particular browser within the last hour. If
not, FileKicker immediately records the click in its history. FileKicker's click reporting is as close to real time as you can find.
7. In processing a file request, FileKicker seamlessly redirects the requester (unbeknownst to them) to one of its
download servers. There, if the requested program has been cached previously, it is downloaded. If FileKicker's download
server determines that the requested file has not been cached, FileKicker simultaneously pulls the file from your web server
and sends it to the user.
8. FileKicker likes to stay on top of things, so once an hour FileKicker's download servers check every
shareware developer's web server for program updates. In this way, FileKicker ensures that your users always
get the most current version of your software. The cost of this process is very low, and it works in much the same way web
browsers do when they go out and check for fresh content.
9. For your reporting needs, FileKicker surveys the server log files daily and calculates the number of bytes
10. On the first day of each month, bills are posted for the previous month's usage, and a new billing cycle begins.