Partners

What the kracker.org think tank does well

What you get when you partner with Graham Brookins and the kracker.org think tank: the disciplines below, practiced on real systems for more than two decades.

• Spec-driven development

  Every build starts from a written specification: what it must do, how it is tested and when it is done. The spec is the contract; the code follows it.

• Agile development

  Short cycles, working software at the end of each one, and plans that change when the facts do.

• Scrum development

  Sprints, a backlog everyone can read, short daily check-ins, and reviews that end in a demo rather than a slide.

• Systems security analysis

  We read your systems the way an attacker would: servers, code, settings and the paths between them, and write down what we find and how to close it.

• Fail-proofing and failure testing

  We break things on purpose before your users do: failing disks, full queues, slow networks, bad input. Then we make the system survive it.

• Security spec design

  Security written into the spec from the start: who may do what, what is logged, what is refused, and how each rule is proven.

• Architecture design

  Systems laid out to last: clear parts and boundaries, room to grow, and nothing that has to be rewritten next year.

• Documentation creation and distribution

  Documentation people actually read, written with the code and published where they look for it, in more than one language when needed.

• Network management

  Hosts, DNS, mail, certificates and the networks between them, run and watched so they stay up.

• Rapid portal application development

  From idea to a portal in production in short cycles: content model, design, features and launch, with nothing left half done.

• Exponential CMS and DXP engineering

  Deep work on the Exponential family of open source products: kernel, extensions, designs, upgrades and releases.

• Upgrades and migrations

  Old eZ Publish installations brought forward to Exponential 6, with their content, their users and their addresses.

• Release engineering and packaging

  Versioned, tested releases on GitHub and Packagist that install the same way every time.

• Performance and hosting operations

  Fast pages and calm servers: caching, tuning, monitoring, and the hosting to run it all on.

…and more. Tell us what you need on the partner program form.

How a partnership works

1. Apply

   Tell us who you are and what you want to build together, on the partner program form.

2. Talk

   We meet, listen, and agree on the scope and the goals.

3. Specify

   We write the specification together, security included, so everyone knows what done means.

4. Build

   Short sprints, each ending in working software you can see and try.

5. Prove

   Tests, failure testing and a security review before anything goes live.

6. Launch and document

   To production, with the documentation your people need to run it.

7. Grow

   We keep it running, measure it and improve it with you.

Who we partner with

• Agencies

  Studios that need a technical partner behind their designs.

• Product companies

  Teams building a product on a CMS, a portal or a platform.

• Open source projects

  Projects that want releases, documentation and security done right.

• Businesses

  Companies with a site or portal that has to be fast, safe and always up.

• Hosting providers

  Hosts that want to offer Exponential to their customers.

• Communities

  Groups that publish together and need a home for it.