EasyD

So here's what it means,

and this is how it works in practice.

Creating a new project

Database into Java code

Generating an API

Managing table data with CRUDS

Relations

Why does this matter?

EasyD benefits

So let's see why you can create APIs faster and more reliably with EasyD.

Out-of-the-box: Audit Trail, Historical Information, Access Rights, Relations, Validations, Authentication, Authorization, Archive, Error Logging, API, Tests, CRUDS (Create, Read, Update, Delete, Search) and much more.

Turning database and project changes into code in a matter of seconds.

Generated code is comprehensively tested and documented.

The generated code is locally accessible (no vendor locks) and human readable.

Less human errors and refactoring.

Very little dependencies.

You know what, this list could go on for a long time.

In summary

Saves Time

Things that used to take days or months are now done in a matter of seconds.

Lowers Complexity

Combining access rights with history is difficult. But don't worry, these things are already done in advance. You just use them.

Increases Quality

Computers only do what they are told to do, and this is a good thing when we want them to produce error-free code.

Who are we and what is our story?

Well, hello there!

My name is Miska, I'm a programmer in my thirties and lead developer of EasyD. I graduated from Aalto University a couple of years ago with a Master's degree in Computer Science (i.e., "Diplomi-insinööri" in Finnish). For whatever reason, I've always been a bit obsessed with finding a way to create perfect APIs. For me, they are the backbone of the internet. However, the process of spending a lot of time implementing a "perfect" API, but later being able to reuse only a fraction of the code, started to feel really frustrating to me. So I thought I would automate this. Yikes, fast forward ~5 years, and I finally think I'm on to something.

Now, it was never my intention to commercialise EasyD. To be honest, I wanted to use it to create commercial software, but I never thought of commercialising EasyD itself. So I always had personal reasons to make EasyD as good as possible, and I think this is reflected in the quality of the tool. Indeed, developing EasyD has always been more of a hobby for me, and I still enjoy it as much as I did when I started.

Although I've been the sole developer of EasyD so far, that doesn't mean I haven't had a lot of help building it. My father Michael has over 20 years of experience in IT consulting and has been closely involved in the design of this tool. This has been important because it has ensured that the practical side of the tool has also been taken into account. But to be honest with you, what has been even more important to me has been all the fun times we have had together.

So what happens next? This is where I hope that you will step into the picture, as we are now looking for partners with whom we can permanently shape the future of the API market.

- Miska Kankkonen, CEO @ Hallittu Oy

I'm a very chatty person, so if you have any questions, please don't hesitate to

or give me a call

+358 40 5790799

Automating API development