About
Built by someone who had this problem for twenty years
Not a platform looking for a market. A specific, irritating, repeated problem that no affordable tool solved, written down as software.
01 Background
Twenty years on your side of the table
I spent two decades running IT for regulated operators — gaming and betting, iGaming platform providers, financial services. Companies between four hundred and two thousand people, with an IT team small enough that everyone knew everyone, and an estate large enough that nobody could hold all of it in their head.
The recurring feature of every one of those roles was an audit, and the recurring feature of every audit was the same question: who has access to this, and who approved it. Answering it honestly took a week of exports, cross-referencing and educated guessing, every single time. Answering it dishonestly took an afternoon, which is why so many organisations do that instead.
02 Integrations
Six post-merger integrations
Six times I merged an acquired company's IT into an existing estate. Six times the same sequence: two directories with different naming conventions, two sets of groups that meant roughly the same thing, a trust relationship stood up to buy time, and a long window in which people held access in both places at once.
That window is where the damage happens. It is also the point at which somebody senior asks for a list of everyone who can reach the payments system, and the only truthful answer is that it would take a fortnight to produce and would be out of date on delivery.
By the fourth integration I had written scripts. By the sixth I had a fairly serious internal tool, and a clear view of the thing it kept proving: the access nobody could explain was not rare or exotic. It was the majority of the interesting findings, every single time, at every company.
03 Why build it
The tooling existed. The price did not.
Identity governance is a solved problem if you are a bank with thirty thousand staff. The established platforms are genuinely capable, and they are priced and scoped for organisations with a dedicated identity team to run them. A twelve-person IT department cannot operate one, and would not be sold one.
Below that line the market offers reporting tools that export a spreadsheet, and compliance products that produce an attractive dashboard from data nobody has verified. Both let you show an auditor something. Neither tells you the truth about your estate.
Intense-Systems exists to put a real answer to "who has access to this, and who approved it" within reach of a company that has four hundred to two thousand staff, one IT team and a certification to keep.
04 How we work
How this company operates
-
Small on purpose
The demo is with the person who built the product. So is the technical call, and so is the answer when something breaks at four o'clock on a Friday. That stops being true at some size, and it is honest to say we are nowhere near that size.
-
Early customers
There are no customer logos on this site because there is no wall of them to show. If you buy now you are an early customer, with the influence over the roadmap that implies and the risk that comes with it. Both should be priced into your decision.
-
Straight answers
If the product does not do the thing you need, you will hear that on the first call rather than in week six of an implementation. Disqualifying ourselves early is cheaper for everyone, and it is the only reason a sceptical buyer ever trusts a small vendor.
-
Where we are
European, working with operators in Malta, Gibraltar, Cyprus and the Isle of Man — the jurisdictions where regulated gaming and financial services concentrate, and where a twenty-person IT function is expected to carry the same control obligations as a bank.
— Founder, Intense-Systems
Come and test the claim.
Thirty minutes, no slides, and a directory that looks like the ones described on this page. If it does not apply to your estate, you will be told.