Websites built to hold up.
Custom Drupal sites, web applications, and the infrastructure underneath. Designed properly, maintained afterwards.
You own what you pay for.
Your domain, your server, your data, your code. No platform you cannot leave.
What we do
Three things, and the second one is the one most studios skip.
Website design and build
The site itself: designed, built, and handed over working.
Care and maintenance
The part most sites are missing. Ongoing work so the site keeps doing its job.
Platform and infrastructure
The things behind the site that only get noticed when they break.
What else we build
Some work does not fit neatly into the three above. These come up often enough to be worth naming.
-
Custom module development
When a site needs behavior that no existing module provides, it gets written properly: tested, documented, and maintainable by someone else later.
-
Integrations and APIs
Connecting a site to the systems a business already runs on — a scheduling tool, a payment processor, an internal database — and writing the API itself when the connection has to work in both directions.
-
Single sign-on and access control
OAuth2 and external identity providers, so people sign in with an account they already have instead of one more password. Roles and permissions set out deliberately, rather than everyone sharing an administrator login.
-
Automation and bots
The work nobody should be doing by hand: scheduled jobs, automated account setup, and bots that handle routine requests and escalate the ones that need a person.
-
Status pages and dashboards
A status page that says plainly whether things are up, and internal dashboards that put the numbers a business actually runs on in one place instead of four.
-
Deployment and version control
Every site is in git, with a documented deploy process and a way back. No editing files on a live server.
-
Security and hardening
Secrets kept out of source control, credentials handed over as one-time links rather than left sitting in an inbox, spam handled without punishing real visitors, and servers configured to a checklist rather than from memory.
-
Visual design and 3D
Modeling, lighting, and real-time work from a game software development background, for the places a site needs more than a stock photograph: product visualization, technical diagrams, and interfaces that were designed rather than assembled.
How it goes
-
01
We talk
What the business does, who you want to reach, and what the site is not doing today.
-
02
A written proposal
Scope, price, and timeline in writing before any work starts. No hourly surprises.
-
03
Design, then build
You see it before it is built, and again as it goes together. Changes are cheapest early.
-
04
Launch and look after
It goes live, and then it keeps working, because someone is still watching it.
One person, and that is the point.
DanK Web Studio is Daniel Kinney. Nearly twenty years building websites and software, and a bachelor's degree in game software development before that.
You deal with the person doing the work. Nothing gets handed to an account manager, and nothing gets quietly subcontracted.
-
Everything is in version control
Every site has a documented deploy and a way back. No editing files on a live server.
-
The site is not finished at launch
Sites rot. Care plans exist because updates, backups, and monitoring are the actual job.
The work so far is electricians, cleaners, and builders. Full case studies are being written up.
Tell us what you are working with.
A short description of the business and what the site needs to do is enough to start. Replies usually go out within a day.