Bottle has no concept at all for this, besides sticking independent applications together. You can do that with Flask as well, in fact the documentation there

Bottle has no concept at all for this, besides sticking independent applications together. You can do that with Flask as well, in fact the documentation there is an entire document describing various approaches[1]. Blueprints are a "new" concept but the approach is basically the same, however they are able to interact with the application at a Flask-level, they can modify the application and share information like the configuration. This is something Bottle doesn't support at a framework level, forcing you to abuse the functionality it provides from a semantical standpoint. This concept is more difficult to understand but than again it is very trivial compared to other concepts any web developer should grasp. [1]: http://flask.pocoo.org/docs/patterns/appdispatch/ http://flask.pocoo.org/docs/patterns/appdispatch/