It is a commercial product. However, since I do feel like I unintentionally stiffed you guys I will push to get it into some hands for free.

Part of the merger included a no-compete clause and required my pulling the repo offline. I would say more but have been asked not to yet. When announcing the project here, I had absolutely no idea that someone  would be interested in acquiring the platform after seeing it here, so I do humbly apologize for a botched launch. On the other hand, I feel like the product that is emerging as a result is more the vision that I had in mind when I set out to create this thing.

This project has been halted as we are in the middle of a merger. More information to be released in the near future.

It has been a while since I've posted an update. We had a few nights of freezing temperatures here in CO and apparently that was too much for my phone lines and they broke. My provider can't get a tech out until next week so that is a bummer. In the mean-time, I have been working on what I can without an internet connection, which is almost nothing. I have, however, started implementing the streaming APIs for the exchanges, with polling as a backup. At the moment, the jawampa library does not support connecting through a proxy so that has been a bit of a hassle. Once my internet is repaired I hope to be able to hammer out the changes and get a new preview out the door.

Mine is open source and free and it looks like C.A.T charges for the core and then for each exchange API integration.

Right now I store all of the trades in an embedded neo4j database and create candles from them as I ready them for the TA to take place.

I think that it makes perfect sense to use the streaming API for the bots. I am starting on the required changes to implement that. The polling bit will still come in handy for keeping the pairs and the balances current but for trade analysis the streaming API makes more sense no matter how I look at it. That will set me back a bit but hopefully it will be pretty quick to implement.

I keep fighting between periodic polling and streaming APIs. Currently I am polling at a configurable interval simply because I'm a bit uneasy about opening the number of connections it would require to subscribe to every channel we are interested in. I may do some tests and see how it performs. I am well aware that using sockets will make response time much better but it would be a relatively large undertaking to switch over at the moment.

I had roughly done that, but now I'm refactoring to make the exchange API consistent across the board. I had toyed with using the open source xchange library which touts support for 50+ exchanges, however I was not able to get it to work reliably enough to be practical. Still aiming to have it ready by the end of the week, but with the holiday Tomorrow, it may be the end of the weekend before a new preview is ready.

Yes. I am currently implementing Poloniex and then will start on C-CEX and Bittrex.

I completely understand the security concerns surrounding a platform like this. That is why I went the route of open-sourcing the entire thing rather than throwing a SaaS platform online, hiding the source, and asking people to trust me with their exchange keys. I do not enjoy that level of liability. I am well aware that there are many bot developers out there and many of them are significantly more knowledgeable than I am in this area. However, these bot developers don't seem to be very keen on providing a beginner-friendly platform to manage the bots as much as a set of scripts that require at least some level of scripting knowledge to setup and use. My goal is more to provide the complete platform for creating, managing and running the bots. And to give the control to the user so that they need not worry about any shady business going on behind the scenes.

As far as security, I wouldn't be comfortable taking it live on a production server yet, but I do try to keep that thought in mind as I refactor pieces of it. I will be posting more information about customizing the core configuration in the next couple of days to help users better tailor the application to their own needs and to increase the security.

Again, thank you for an objective opinion and I look forward to more feedback.

There is a readme in the zip file with instructions on running it. But for simplicity sake, just run the jar using java -jar acctbot-v1.0.0-alpha.1.jar. Wait for it to give you the started message in the console and then in your browser, navigate to https://localhost:6160. It includes a bundled self-signed certificate so you will receive a warning about that. Just proceed past the warning and follow the steps in the (very rough) setup wizard.

Thank you for the suggestions. I will take a look at the APIs tonight and start getting them implemented. The application was written with multiple exchanges in mind so it shouldn't be a huge undertaking.

Thanks for the interest so far. Currently Cryptsy is the only exchange supported, simply because that's where my coins are. I will begin implementing more exchanges this evening as I can see that there are some concerns with Cryptsy at the moment. I am open to suggestions on the next exchange to implement. I will plan to drop a new build within a week with a new exchange added and more bug fixes. Any other questions or suggestions are most definitely welcome!

Hey all! A couple of months ago, I started working on an automated trading platform for Cryptsy. As I'm getting closer to a stable release I decided it was time that I released a developer preview so that I can start getting feedback from the community. It is a Spring boot web application, runs on Mac, Linux and Windows, and is ready to run out of the box without any database or web server installation required.

It currently supports a handful of indicators and safeties with more to be added as I go. Right now it only supports Cryptsy, but I will be adding more exchanges after more bugs are ironed out. It supports both simulated and live trading, price alerts, push notifications via Pushover and desktop notifications.

The project is open source under the GPLv3 license and the code is available on GitHub at https://github.com/AcctCapital/AcctBot

If you are interested in getting your hands on the developer preview it can be found here https://github.com/AcctCapital/AcctBot/releases/tag/v1.0.0-alpha.1

You can follow the project on Twitter here https://twitter.com/AcctCapital

Or follow the blog (with screenshots) here http://blog.acctcapital.com

This is currently a side-project, but I put a lot of hours into it and I would like to have some community involvement to finally bring to the open source market, a trade bot that rivals the paid solutions. I have a lot planned, but it can only be made possible with the feedback and advice of the potential users.

Thank you for reading and if you have any questions, suggestions, or concerns, please let me know!