Skip to content

Home

Jump to bottom Edit New page
Chris Magnuson edited this page Dec 10, 2015 · 7 revisions

Overview

ELK Banking is designed to be an open source, permissive license, privacy minded, personal finance monitoring software.

Some of the key features of the software would be:

  • Download all personal financial transactions over time
  • Provide a means to explore, graph, and alert on your financial data
  • Serve as an automated means to ensure that if you finances are under control
  • Show you plainly where you are at and where you are going financially

Trello board used to track development and features.

#Installation This process is tough and is an area that will be improved upon but I have opted to release what I have, however difficult to install and setup, in the hopes that if I am never able to work on this again I have at least provided someone else a starting point to move forward from and that anyone who is willing to take the time to follow these steps can actually reap the benefits of this software now without waiting for some more mature easier to setup future version that may never happen.

I will walk you through the process of recreating the environment I use to run and develop the software, any deviation for this for now will have to be worked out by you until we can get a nicer setup process in place.

Steps to get your ELK Banking instance going please install the following:

  • arch linux
  • aura
  • meteor using sudo aura -A meteor
  • ELK stack sudo pacman -S elasticsearch, sudo aura -A logstash kibana
  • git clone https://github.com/ChrisMagnuson/elkbanking

Steps to start up your ELK Banking environment:

  • sudo systemctl start elasticsearch kibana
  • cd elkbanking && meteor

#Plans for the future My intent is that one day there would be service providers running this software and that at least a zero knowledge version of this software exists that would allow only the user of the service and not the service provider to access their data.

This document is subject to change and only reflects my current intent. As I or others build out this software its licensing, use cases, privacy model, etc. may all be subject to change and the statements above should not be construed as a contract that will be held to, but a philosophy that is the starting point for this project and will evolve and mature over time.

There are questions that have not been fully answered yet, like is it better to get a free non-secure option out there so that the software is used by a larger population of people with a more secure zero knowledge paid offering available or is it better to only offer the secure option and accept the loss of users that could help perfect and evangelize the product?

I lean towards only offering a secure version at the point where this software is run by a service provider. I don't think I want the ability to subvert my user's privacy so that I cannot be forced to do so in private like was attempted with lavabit.

I lean towards offering an insecure version that can be installed and run on anyone's own computer as they might secure their own instance through other means (run everything locally on a disk with full disk encryption).

#Licenses in use

Add a custom footer
Add a custom sidebar
Clone this wiki locally