First Open Source (J2EE), Low Code, Mobile Development Platform

Automatic Mobile Integration
- Generate native SDKs tailored to your server data
- Conveniently map client data to relational databases
- Code natively

Cross-Platform Data Portability
- Simplify your stack
- Develop easier than "mobile web"
- Increase data Agility via typesafe client models

True Open Source
- Own the entire run-time stack, and run wherever you like
- No vendor lock-in
- SaaS hosting available

Data Aggregation
- Drag-and-drop
- Automated model extractors
- Aggregate from disparate databases including Oracle, MySQL, PostgreSQL

Portable Web Forms
- Generate beautiful React.js forms to kickstart web development

Flexible Architecture
- End-to-end Typesafety
- Mix-and-match with other "best-of-breed" tools

Plays Well With Others
- Mule ESB (Mulesoft)
- Realm.io mobile database
- JPA
- Ruby Models

Supported Platforms
- Android
- Ios
- Backed by a turnkey, open-source, J2EE server featuring live model injection

View our Data Sheet here

How It Works

Below is a screenshot of the CAM editor with our database structures on the right, and our client model on the left. We created our client model via drag-and-drop from a sample PMIX database schema. A recent blog post explains the motivation for this in a bit more detail. CAM screenshot
One powerful feature of CAM is the ability to create Data Dictionaries for both our client and server models. There are several videos on this topic including: https://www.youtube.com/watch?v=aY7G48hQGEk..

Once we create our client models in CAM, we import them into the Splicer server, which generates our client and server models. The server models automatically connect to our relational data using JPA, while the client models expose the server data to our Droid and IOS developers as typesafe "pojos" or "DAOs".

We plan to offer a freeware version where you can create your own models, so check back here or email info@splicer.io, and we'll keep you in the loop. We currently offer only a commercial version of the development suite and server.

Why is it different?

With Splicer, the client's data objects are typesafe and guaranteed to correlate to your server model. These client DAOs allow the mobile developer to access the server's database just like a server-side ORM does. When you change your model, compilers show where your client code breaks due to model changes. If you have multiple types of mobile apps, this type of Model Management will save your sanity.

Splicer System Architecture

Splicer Architecture

Wouldn’t it be great to access server data as typed objects?

Splicer extends server data structures to the top of the client stack
  • Easily manage multi-app integration
  • Focus client coding responsibilities on user interaction ("View" coding)
  • Modify your system model synchronously with ease, confidence, and Agility
  • Compilers validate code conformity to model changes
  • A true "low code", enterprise infrastructure


We can spin up an AWS instance for you today. Email info@splicer.io so we can set you up a sandbox for you. Send us your database schema and we will spin up a full, custom J2EE server typically within a day.