Help
Four kinds of people land here, and they need four different things. Find yours below.
I am evaluating d1kit for a project
The documentation covers what the platform provides - financial accounting, inventory - and the interfaces a deployment exposes. After that, talk to us about your case.
Read the docsI need to integrate with a deployment
REST, GraphQL and webhooks are documented here. Credentials are issued by the organisation that operates the deployment, not by us.
See the interfacesI want to learn, or start as an intern
The learning guide has been open since 2017 and the classes are free to join. Interns get structured work with review, and a defined route to paid project work.
Start learningI am a user of a system built on d1kit
Support for a deployed system comes from whoever operates it - your hospital, agency or the firm that built it. We cannot access or change your data.
Why that isCommon questions
Is d1kit open source?
Not publicly. The platform and its modules are made available to community members and partner firms under an access agreement. This site documents what the platform provides and how to integrate with it, so you can evaluate it properly before asking for anything.
Why is the technical documentation not published?
Systems built on d1kit hold financial records and beneficiary registers for organisations accountable for protecting them. Publishing the internals of the platform those systems run on would give anyone studying it a head start they have no business having. Capability is public; implementation detail is shared with people whose identity we know.
What can d1kit actually do out of the box?
Financial accounting - chart of accounts and double-entry ledger, budgeting, procurement, remittances, receivables and payables, bank reconciliation and reporting. Inventory and supply chain - multi-location stock, requisitions, goods receipt, vendor-managed inventory, stock counts and valuation. Around those sit approval workflow, role and privilege management, document handling, notifications and dashboards.
How do I connect another system to a deployment?
Three interfaces: a REST API for defined operations, a GraphQL endpoint for related data in one round trip, and webhooks for event notification. Credentials are issued per deployment by the organisation that operates it, with their own permissions, expiry and rate limits. Integration does not require community membership.
Do I need to be a member to integrate?
No. Integration is a matter between you and the operator of the deployment. Membership is for people building on the platform itself.
Can I use d1kit for a commercial client project?
Yes - that is the normal case. Several independent firms deliver client work on it. The access agreement covers what you may redistribute, which is the platform itself, not the application you build on it.
I am new to development. Where do I start?
The learning guide, which has been openly published since August 2017. It maps what a working developer needs to be knowledgeable in, well beyond programming. Then join a free class, then apply for an internship - the guide page explains the whole route.
Are internships paid?
Not at the earliest stage, and we would rather say so plainly. What we commit to is real work, real review from an experienced developer, and a defined route to paid project work rather than an indefinite queue. Members who reach the advanced stage join project teams as consultants and earn from delivery.
I found an error on this site. Where do I report it?
Use the contact form. Include the page and what you expected it to say. Corrections from people reading it for the first time are the most valuable ones we get.
What we can and cannot help with
d1kit is a framework, not a hosted service. Deployments built on it are operated by the organisations that own them - a hospital, a government agency, or the firm that delivered the system. Those operators hold the data and the accounts.
That means we cannot reset a password on a system you use, look up a record, or change a configuration on a live deployment. If you are a user of such a system, your route is the organisation that gave you the account.
We can help with the framework itself: how it works, how to build on it, how to integrate with it, and how to get access to it.
Contact a maintainer
One form, read by a person. Use it for documentation errors, access requests, partnership enquiries and framework questions the docs did not answer.
Open the contact form