An error occurred
27 |29 | ${data.message} 30 |
29 | ${data.message} 30 |
38 | ${data.message} 39 |
44 | ${data.message} 45 |
46 | ${data.message} 47 |
44 | ${data.message} 45 |
5 | Your interval will place a ${data.method} request to ${data.url} 6 | every ${data.interval_unit_count} ${data.invertal_unit_type}s, for 7 | a total of ${data.duration_unit_count} ${data.duration_unit_type}s, 8 | and a total of ${data.invocations_count} invocations, with 1 occurring 9 | immediately after purchase. 10 |
11 | Do you wish to proceed to purchase, and start your interval? 12 |
68 | The system is robust, fault-tolerant and scalable. Normally you can purchase either a subscription, or a one-off timer. But this is a free demo API key for HN readers to try it out without paying anything. 69 |
70 | Pocketwatch provides Pocketwatch Timers which are your schedulers for recurring tasks that can issue HTTP requests at intervals as fine as 1 second, or longer. 71 |
72 | You can use them to: 73 |
POST /purge-cache every 15 minutes
75 | POST /check-status every 10 seconds
76 | GET /tweet-web-crawl every 1 minute
77 | PATCH /run-chromeless-tests every 5 minutes
78 | all the things you might use cron/crontab
for (or systemd
timers for), but when you want it more scalable, more fault-tolerant than one machine running cron
— you use Pocketwatch Timers.
80 |
Just fire and forget. 81 |
Just pick an interval (say, 3 seconds), and a duration (say 5 weeks), set your URL and HTTP method, and you're good to go. 82 |
148 | This demo uses an API key I set up specifically for HN readers. The key is i_am_hn_and_proud
. To save resources, any timers created with this free demo key will only last roughly 2 weeks regardless of the maximum duration you put, and the key itself also has a maximum number of timers and hits. You can also try other HTTP methods, and include a body and Content-Type
for the requests by using this key with the API directly. If you'd like to use the API directly, see the docs, and if you use Node.js, get the Node.js client library. By using this demo you also agree to the terms. If you have any issues, open one here to let me know.
149 |
60 | On-demand Pocketwatch Timers are schedulers that can issue HTTP requests at intervals as fine as 1 second, or longer. 61 |
62 | You can use them to: 63 |
all the things you might use cron/crontab
for, but when you want it more scalable, more fault-tolerant than one machine running cron
— you use Pocketwatch Timers.
69 |
Just fire and forget. 70 |
68 | The system is robust, fault-tolerant and scalable. Normally you can purchase either a subscription, or a one-off timer. But this is a free demo API key for Product Hunt readers to try it out without paying anything. 69 |
70 | Pocketwatch provides Pocketwatch Timers which are your schedulers for recurring tasks that can issue HTTP requests at intervals as fine as 1 second, or longer. 71 |
72 | You can use them to: 73 |
POST /purge-cache every 15 minutes
75 | POST /check-status every 10 seconds
76 | GET /tweet-web-crawl every 1 minute
77 | PATCH /run-chromeless-tests every 5 minutes
78 | all the things you might use cron/crontab
for (or systemd
timers for), but when you want it more scalable, more fault-tolerant than one machine running cron
— you use Pocketwatch Timers.
80 |
Just fire and forget. 81 |
Just pick an interval (say, 3 seconds), and a duration (say 5 weeks), set your URL and HTTP method, and you're good to go. 82 |
148 | This demo uses an API key I set up specifically for Product Hunt readers. The key is i_am_ph_and_proud
. To save resources, any timers created with this free demo key will only last roughly 2 weeks regardless of the maximum duration you put, and the key itself also has a maximum number of timers and hits. You can also try other HTTP methods, and include a body and Content-Type
for the requests by using this key with the API directly. If you'd like to use the API directly, see the docs, and if you use Node.js, get the Node.js client library. By using this demo you also agree to the terms. If you have any issues, open one here to let me know.
149 |
CronStorm manages the infrastructure required for to run millions of cron jobs on time. CronStorm's FailureGuard technology keeps executing your jobs even under partial system failure.
Is how often you can schedule your jobs, at no extra cost. Most competitors only get to 20 seconds, and charge extra, making CronStorm the choice for triggering collection of fast-changing data. 49 |
CronStorm is great for recurring actions such as periodically gathering data from the web into a feed. It’s also ideal for cleaning up logs, kicking off routine backups, and integrating into your app with CronStorm API. 55 |
69 | 70 | Starter. 71 |72 | |
73 |
74 | 75 | Business. 76 |77 | |
78 |
79 | 80 | Enterprise. 81 |82 | |
83 |
---|---|---|
88 | 89 | Side project. 90 | 91 | |
92 |
93 | 94 | Recommended. 95 | 96 | |
97 |
98 | 99 | Web scale. 100 | 101 | |
102 |
105 | 106 | 5,000,000 requests a month. 107 | 108 | |
109 |
110 | 111 | 25,000,000 requests a month. 112 | 113 | |
114 |
115 | 116 | 125,000,000 requests a month. 117 | 118 | |
119 |
122 | 123 | 100 cron jobs. 124 | 125 | |
126 |
127 | 128 | 1,000 cron jobs. 129 | 130 | |
131 |
132 | 133 | 10,000 cron jobs. 134 | 135 | |
136 |
139 | 140 | Email support in 3 days. 141 | 142 | |
143 |
144 | 145 | Email support in 1 day. 146 | 147 | |
148 |
149 | 150 | Phone support in half a day. 151 | 152 | |
153 |
185 | The CronStorm API lets you create cron jobs that will issue web requests at intervals, right from your application. 186 | Read the CronStorm API Documentation. 187 | The CronStorm CLI lets you easily access the full power of CronStorm from the command-line. 188 | Get the CronStorm CLI. 189 | When you want a more scalable, fault-tolerant and powerful scheduled task than cron provides — you use CronStorm. 190 |
5 | Your interval will place a ${data.method} request to ${data.url} 6 | every ${data.interval_unit_count} ${data.invertal_unit_type}s, for 7 | a total of ${data.duration_unit_count} ${data.duration_unit_type}s, 8 | and a total of ${data.invocations_count} invocations, with 1 occurring 9 | immediately after purchase. 10 |
11 | Do you wish to proceed to purchase, and start your interval? 12 |
17 | These terms are between you and CronStorm ("we", "us"). 18 |
19 | When you subscribe to the CronStorm API service to get a developer API key, you agree to these terms. If you cancel your subscription (which you can do at any time) we do not provide a refund for partial months, but instead your subscription (your API key) will remain operational until the end of that billing cycle. Billing cycles begin each month on the same date that you started your subscription, or the closest day to that. 20 |
21 | If you provided an email address when you paid (you may have had to do so, since Stripe (a payment provider we use, not affiliated with us) may require it), therefore you agree that you consent to us sending you some promotion mails about your subscription, reminders about subscription, overdue payments, and support emails about your service, or other notifications over email. If you wish to not receive these mails then you can email us at this support address to opt out and we will no longer contact you, except as we are required to do so by law or to resolve or clarify any issues about payment that, if we were not to contact you, would possibly have adverse legal consequences. 22 |
23 | When you buy an interval you purchase a number of invocations. But actually that number is only the maximum number of invocations. The actualy invocations effected are always less than that because each request always takes slightly longer than the interval duration ( for example, a 1 seconds request typically takes 1.1 seconds ), so that means that over a 5 minute ( 300 invocation ) duration, you will typically only see about 270 invocations. This is normal. What you are in effect paying for is utilizing of our system for the specificied duration of time, which is always exact. But the number of invocations we provide at time of sale is only a guide and you agree to take it as such. If you have a need for a specific number of invocations ( rather than a specific exact duration over which they occur ) please contact us via email or raise an issue on our github issue tracker. 24 |
25 | This is the beta release of pocketwatch. Currently limitations include (but not limited to): GET requests only, 26 | cannot delete an interval once it starts without knowing it's tracking number (long, secret code which you need to save 27 | if you want to prove you created the interval and want to request its deletion, currently request is via email). 28 |
29 | If you do request an interval deletion we do not currently offer any refunds. So please begin your intervals carefully. We can delete it for you if you request it (and have the tracking number) but you will not get any money back. 30 |
31 | Use this tool at your own discretion. We are not responsible for how you use it. 32 |
33 | We reserve the right to delete intervals with no refund if it appears they are harmful in any way. 34 |
35 | In general we will not offer refunds. But in case we do, they will be determined on a case by case basis. 36 |
37 | Don't use the names The Dosaygo Corporation, DOSY, Dosycorp, or CronStorm.com in anyway that suggests partnership or endoresment or other relationship when none in fact exists. 38 |
39 | This product is offered by the Dosyago Corporation, any legal action will be decided with respect to the laws of the United States, and through the courts in that jurisdiction. 40 |
41 | Unless otherwise made explicit, no content or other corpyrightable or protected work may be reused or incorporated without prior written permission from us. 42 |
43 | If you need to contact us open an issue at: https://github.com/dosyago-corp/service-issues/issues 44 |
45 | We do our best to place and fulfill your orders as requested, and to achieve the specified rates of requests for the specified duration as ordered in your interval, however we do not guarantee we shall achieve this, and we are not responsible for issues related to external network latency, routing or other such issues, and in the case your interval suffers degraded performance on account of such or other issues we have limited control over, we certainly offer no refunds. This service does not currently have any SLA ( service level agreement ). 46 |
47 | If you need to contact CronStorm privately please email CronStorm for help. 48 |
49 | These terms are a living document. We may update them at any time, with or without notice. 50 |