Request access

d1kit is a community-driven ecosystem. This site documents what the platform provides; the framework itself, its modules and its technical documentation are shared with community members and partner firms under an access agreement.

Why access is granted rather than open

Systems built on d1kit hold financial records, beneficiary registers and operational data for organisations that are accountable for protecting them. Publishing the internals of the platform those systems run on would hand anyone studying it a head start they have no business having.

So the platform’s capability is public - enough to evaluate it properly, and enough to integrate with a deployment - while implementation detail sits behind an agreement with people whose identity we know.

Who it is for

Developers joining a project team. You are going to work on a system built on d1kit, at one of the firms that uses it, and you need to become productive.

Partner firms adopting the platform. You deliver software to your own clients and want to build on d1kit rather than assemble the same operational backbone yourself. Partner firms hold their own client relationships and run their own deployments.

Students and independent developers who have worked through the classes and want to build something real. This route depends on cohort capacity - the online classes are the place to start, and they are open to everyone with no approval needed.

What membership provides

• The framework and the shared module set
• A container image that boots a working deployment, so you can learn against a running system
• A place in the class cohort that walks through building a real module
• A first task with review from an experienced maintainer
• The technical documentation that is not published here

What it does not provide

• Access to anyone’s deployment. Live systems belong to the organisations that operate them.
• Client-specific modules. Work built for a particular organisation stays with the firm that delivered it.
• Ownership of the platform. You may build and sell applications on d1kit; redistributing the platform itself is what the agreement governs.

What is expected in return

• Keep shared material shared. Do not publish it, and do not paste it into public forums or third-party services.
• Report security concerns privately, through the contact form, and never test against a deployment you do not operate.
• Do not name clients in shared code, commit messages or discussion. Deployment specifics stay out.
• Contribute fixes back where you fix something in the shared set.

Before you apply

Read the introduction and whichever of financial accounting and inventory is closer to what you intend to build. If you are integrating rather than building, the REST, GraphQL and webhook pages may be all you need - integration does not require membership.

How to apply

Use the sign-up form, and tell us who you are, what you have built before, which route applies, and what you intend to build.

A maintainer reviews applications, usually within a few working days. You will get either an invitation or a specific reason it was declined - not silence.