Cloudfier FAQ

What is Cloudfier?

Cloudfier is a platform for rapid development and deployment of data-centric business apps. Think of a MS-Access and FileMaker Pro that is made for the cloud and takes software engineering seriously.

Cloudfier is a problem-domain-centric tool: once you describe your solution in terms of your problem domain, Cloudfier will produce and deploy a functional application that includes business logic, a database schema, a user interface and a REST API.

Who is Cloudfier for?

Consultants, independent developers, in-house IT departments building bespoke data-centric business apps that want to do it fast and right!

Why the emphasis on domain modeling?

The business domain model is the blueprint of an enterprise application.

Why should I use Cloudfier instead of Grails/Rails/Django?

RAD frameworks such as Rails, Grails and Django are competing alternatives for building data-centric business applications. But they are too technology-centric. Cloudfier’s approach promotes a clear separation between technology and problem domain concerns, achieving full scale platform independence as a way of life. The same Cloudfier application can run on a relational or NoSQL database, or on EC2 or Google App Engine, as a web app or as a mobile app with no changes to the application.

How much does Cloudfier cost?

Cloudfier is still under development and is currently free. The plan going forward is that plans that allow deploying applications into production will have a fee based on usage. Prototyping and development are likely to remain free.

Is Cloudfier open source?

Yes. See cloudfier on github.

Is Cloudfier a prototyping tool or a production tool?

Both… soon. Right now, Cloudfier is available as an early beta and is not recommended yet for deploying applications into production. It is a fine prototyping tool as it stands right now though.

Can a Cloudfier app do this or that?

The Cloudfier Feature List is your friend!

How do I do this or that in Cloudfier?

The How-to page is your friend!

What could possibly go wrong?

Known shortcomings that should be addressed in the future.

Name clashes in JEE generation if you name your role class “Profile”.

Didn’t find your question here?

The issue tracker is the best place to ask your questions.