Questions we get asked

The senior engineer leading your project. They write code on it, and they're the person in your review meetings.

During the assay, yes, because it's faster to sit with the people who use the system. During the build we work remotely, with regular sessions together. Blueforge Digital LLC is registered in Sheridan, Wyoming.

Yes. We work in your repositories and follow your review and release process where you have one.

[Typical project size is confirmed before launch]. If yours is too small to need this level of rigour, we'll tell you.

The assay is fixed price. The build is quoted after the assay, against a scope and pass criteria we agree together. The engagements page explains each one.

It will. Each change gets a short written note with its effect on cost and dates, and nothing starts until you've approved it.

No. They're billed to your own accounts.

You do, from the first commit, in your own repository.

Source code, infrastructure scripts, architecture documents, runbooks, the decision log and every account, all in your name.

You can. The documentation is written so a competent team can take over without calling us.

Named accounts, the least access the work needs, and everything revoked at the end. [Security certifications are listed here once confirmed].

Not by us. The vendor settings and contract terms that prevent it are checked in the assay and documented.

Yes, before we see anything sensitive.