Core banking components
Ledgers, account structures, fee and limit engines, treasury automation, reconciliation reporting.
Services
What we take on
Three lines of work: building software for financial companies, advising on the technical side of running it, and compliance work from fixed-scope packages to an outsourced function.
Custom software development
We build in the financial domain, on the back of a payment platform we run in production. Most engagements start from a module on Beeqeeper or from a system the client already runs.
Work for payment and e-money licence holders
Payment flows, approval and four eyes controls, client onboarding with KYC, and reporting a supervisor will ask for.
Integrations
Bank adapters, SEPA messaging, blockchain nodes, KYC and AML providers, FX rate feeds.
Technology and IT consulting
Advice from people who run a payment platform in production.
Architecture reviews
System structure, data flows, failure points, and where the line runs between building and buying.
Integration and vendor choices
Which bank, KYC or custody provider fits the flow you are building, and what each integration costs in engineering time.
Security and access
Authentication, role design, audit trails, and the evidence a supervisor asks for. We hold no ISO 27001 or SOC 2 certificate today and say so up front.
Compliance as a service
An outsourced compliance function for payment and crypto companies, plus fixed scope packages. You fill in a questionnaire, we draft on templates we use ourselves, then we hand over on a call and stay available afterwards. You keep the source files.
-
MiCA readiness
A readiness review and the documentation set a crypto asset service provider needs for its application. Three to four weeks.
-
DORA gap scan
Where your ICT arrangements stand against DORA, what is missing, and what has to be written to close it. Two to three weeks.
-
AI compliance starter
A baseline set of policies and records for teams putting AI into a regulated process. Two weeks.
-
Who writes them
People who write and maintain compliance documentation for regulated financial companies as their daily work. One of them holds an ICA certification.
How we work
The same four steps on every engagement.
-
Scoping call
You describe the licence, the currencies, the volumes and what already runs. We say what is realistic and what is not.
-
Fixed scope specification
A rough estimate first. Then a specification with a fixed scope and dates, agreed before anyone writes code.
-
Build and review
We ship in increments against the specification, with a review at the end of each one.
-
Handover and support
You get the working system and its documentation. Support continues under the agreement.
Your data
The boring guarantees, stated plainly.
NDA is standard
We sign before we see anything.
No training on your data
External models are not trained on client documents.
No silent retention
Documents are not kept beyond the support window unless you ask us to keep them.
Languages we work in
Czech and English.
Tell us what you are building
Describe what you run or plan to run. We will say what is realistic, and what it takes.