anchor.diff:  ** Invoice: invoice generation and management (e.g. ability to adjust invoice items) for subscriptions and one-off charges
   ** Payment: payment gateways integration for recurring and one-off payments
   ** Overdue: dunning management (in case of unpaid invoices for instance)
  +* Multi-tenancy: Kill Bill has been designed as a multi-tenant system, meaning **you can run multiple logical instances of Kill Bill with a single server and database** (see this http://killbill.io/blog/subscription-service-using-kill-bill[blog post] which illustrates some of the use cases).
   * Plugins
  +** Ability to easily connect to third party services
  +** Ability to modify behavior of the system to match custom business logic
   
  -Kill Bill supports multi-tenancy, meaning you can run multiple logical instances of Kill Bill with a single server and database (see this http://killbill.io/blog/subscription-service-using-kill-bill[blog post] which illustrates some of the use cases).
   
   
   == Where to Start?
   
  -TODO points to 
  +//TODO points to Getting Started
   
   === Layman's Next Steps
   
  
positive.code: ** A *plugin framework* where open-source and proprietary plugins can be added to modify the behavior of the system, and/or to interact with third party systems
  ** A robust persistent *event bus*, that is used both internally and externally (events are visible to plugins and to other services via HTTP push notifications)
  ** An *auditing* framework that keeps track of all the changes that occurred (who?, when?, what?)
  * Core services, each of which exposing its own APIs and publishing bus events, which are consumed by other core services or plugins:
  ** Account
  ** Catalog
  ** Subscription and entitlement
  
negative.code: 
  So, in the diagram above, we can see that:
  
  * Customers interact with your website, which then issues REST API calls to Kill Bill. **You are responsible for designing and building that piece**.
  * Kill Bill, with its database, **manages all the state associated with the subscriptions, invoices, payments, etc.**
  * KAUI is the **Back-office UI for your teams**, and it includes role based access control to provide different priviledges for different teams/users:
    ** Your customer support team will use to access/modify consumer accounts data
    ** Your product team  will use to configure catalog information, billing rules, ..
    ** You finance/accounting team will access it for different types of reports
    ** Your engineering team will access it for running quick dev scenarios
  
  
  === Deployment
  
  Kill Bill is packaged as a WAR and is therefore executed within a web container (typically Tomcat). While you can deploy Kill Bill directly as a WAR inside a container, we also provide easier deployment options:
  
  