Why do we choose Clojure

Clojure is a functional programming language, written for those who seek simplicity. The combination of a better way to build and hire top talent can help a company to move faster.

We started IPRally with Clojure because of my personal love story with the language. Before IPRally, I was working as a developer in Adtile, working with a globally distributed analytics pipeline. We had the code organized in Clojure microservices, and the crazy thing was that the code was easy to understand. Not only that, it was easy to modify. We had tests for the microservice functionalities, but not for the finer details. Then without changing the tests, you could fearlessly modify the solution, refactoring the code into something comprehensible. Because the language is so powerful, such high level tests can be enough.

Data is kept in simple format. When you can understand the data, the code makes more sense too.

What is this language

Clojure is a modern reincarnation of Lisp, an ancient language already specified in 1958. In fact, the original Lisp is the second oldest high level programming language after Fortran. It was favored especially among the artificial intelligence researchers. Clojure, the Lisp of today, is often used with web development, with integrations to both Java and JavaScript ecosystems. Lately there has been some movement towards the AI roots too with support for Python interop and Clojure data science libraries like Deep Diamond.

You don’t usually learn Clojure as your first language, nor do you accidentally end up writing Clojure in the industry. That’s why studying it tends to be a conscious choice, and that’s why the Clojurians tend to come with some seniority, and are among the highest paid programmers.

We use ! in the end of function name if running it may have side effects. In this case, you are the machine.

Simple > easy or safe‍

At the end of the day, programming is mostly about building. There certainly are difficult challenges, e.g. natural language understanding, but mostly we developers focus on building systems in a maintainable way. And it’s not just about technical debt. Systems can be built in endlessly different ways, which of most eventually slow you down and cause suffering. When you compromise your solution slightly with every decision, you cannot fix it with just some refactoring. Building in a maintainable way is crucial for a product company - it eventually leads to a faster development speed and allows scaling up the organization.

Clojure opts for simplicity. As a comparison, Ruby is a language that tries to make things easy. But the Clojure way is to care less about how fast you can code, and more about minimising magic. Rich Hickey's classic presentation on the subject comes recommended. Other languages like Java or Haskell choose safety, with type systems for data. With Clojure, the responsibility for creating safety nets is left for the developer. Advantage? In good hands, this can avoid complexity. Here is an example how 441 lines of idiomatic Java become 58 lines of Clojure.

The right thing to do, even if it’s hard

‍Aiming for simplicity makes one respect craftsmanship. No technology guarantees a simple solution. There are always more ways to create a mess than to find something elegant. Simple is hard, and we still choose simple. In the long run, a simple solution is more maintainable and safer than something more complex. 

You surely can create a good solution with any moderately sensible technology. In the end of the day, developers matter more than technology or the processes, and the main advantage of Clojure comes from this. The developers who love programming and go the extra mile for learning a rare language are often pretty good ones. We met with two of the earliest IPRally team members, Juho Sepänmaa and Sebastian Björkqvist, in the Helsinki Clojure meetups. Even though Sebastian ended up working with deep learning and Python, Clojure helped once again to spot a top talent.

The syntax for figuring out the good startups has never been simpler.

We are building a tech organization with foundations in Clojure philosophy. We have a position open for Clojure developers. You can also just send me an email at juho@iprally.com.

Read more

Webinar Q&A follow-up: your questions about the IPRally MCP answered

Thank you to everyone who joined Patent answers, inside the AI you already use. Across the two sessions on 4 November, you sent us more questions than we had time to answer live. We have grouped them by theme below, merged similar questions and included the answers given during the sessions.

Your IPRally workspace, wherever you work

Your AI assistant can now pick up where your IPRally work left off. The IPRally MCP now reads your collections, tags, search cases, projects, and agent runs, so your agent starts from results you’ve already vetted instead of a blank prompt.

Webinar Q&A follow-up: your questions about IPRally Drafting answered

Thank you to everyone who joined No more drafting in the dark: prior-art-aware patent drafting with IPRally Protection. Across our EU and US sessions, you sent us more than 80 questions, from file formats and drawings to claim clarity and US disclosure duties. We have grouped the answers by theme and merged similar questions. Some were answered live or in the chat during the sessions, and we include those here too.

Webinar Q&A follow-up: your questions about IPRally Intelligence answered

Your questions on IPRally Intelligence, answered: from working with larger datasets to verifying results at paragraph level.

IPRally is SOC 2 Type II compliant

IPRally has completed its SOC 2 Type II examination. Advantage Partners, our independent auditor, tested our security controls in operation from March 4 to June 4, 2026, and issued an unqualified opinion: no exceptions noted on any control tested.

When systems start talking: IPRally's journey toward a virtual IP department

Something new is happening: people talk to systems in plain language, systems talk back, and systems have started talking to each other the same way. As AI climbs from the small decisions to the large ones, the question for IP work is no longer whether it gets automated, but how to stay in control once it is. Co-founder and CPO, Sakari Arvela, lays out where this leads – through IPRally's new API and upcoming MCP support toward a virtual IP department that's always on – and why humans end up more important in that picture, not less.

Search, Intelligence, Protection: the three pillars of IPRally’s next chapter

For nearly a decade IPRally has been obsessed with getting one task right: patent search. Having built the best patent search in the world, we’re now reorganizing around three pillars – Search, Intelligence, and Protection – the newest of which makes drafting prior-art-aware from the first sentence. Co-founder and CPO Sakari Arvela maps out the next chapter, and why Protection is the shift he's most personally invested in.

NGen selects IPRally to bring AI-native patent intelligence to Canada's advanced manufacturers

After evaluating a range of tools on functionality, usability, and cost, Canada's Global Innovation Cluster for Advanced Manufacturing chose IPRally to power its Patent Search Adoption Tool Pilot Program.

IPRally and RPX Corporation announce strategic collaboration, cross-linking AI-powered patent search with RPX Empower

IPRally today announces a strategic collaboration with RPX Corporation, the global patent risk management service provider, that further expands the capabilities of the RPX Empower platform and provides seamless access to business critical complementary information for IPRally users.

Macro meets micro: IPRally's next chapter builds intelligence on search

Excellence in patent search was always the foundation. But foundations are meant to be built on. After years of staying focused – and saying no to a lot – IPRally is now ready to bring the same rigor and precision that redefined search to the bigger, strategic questions that businesses make decisions on. CCO Andreas Cehlinder explains why now, and what comes next.