Vol. IV · Functory Quarterly№ 001 · Edition 2026
I
The model

We build it
with you.

An engineering firm, and the platform behind it.

We build production systems for companies who need one, end to end. The platform underneath is why we can quote in weeks: identity, commerce, workflows, search and 200+ primitives are already built and tested on well-architected compute, persistence, and messaging infrastructure, so an engagement focuses on what makes your product unique. Everything we ship runs in your own AWS account, preserving data sovereignty and integrity.

01

Scoped to outcomes

You buy a working system, not a seat count. Discovery produces a fixed quote before you commit to a build.

02

Built on the platform

The primitive library does the undifferentiated work, so the engagement focuses on your domain.

03

Yours at the end

Your AWS account, your code, and well-defined, permissive escape hatches. The system outlives the engagement.

II
The engagements

Four shapes of work.

Discovery is designed as the starting point. Nothing obliges you to take the next step, and the plan you leave with is yours either way.

fig. ii·a7 deliverables

Discovery

We map your domain, size the work, and hand back a plan you could take to any team.

2 weeks

fixed scope, fixed fee

What you get

  • Domain and entity model for your product
  • Target architecture in your AWS account
  • Capabilities briefing on what is built, and extensions to bridge the rest, by us or by you
  • Delivery plan with milestones and sequencing
  • Fixed quote for the build engagement
  • Cost projection against your real workload
  • Written recommendations, yours to keep

Best fit

Teams with a product in mind and open questions about scope, cost, or sequencing.

Book a consultation
fig. ii·b7 deliverables

Build

We build and ship your system on the Functory platform, into your own AWS account. Where a starter kit already fits your domain, that starts close to day one.

0 to 8 weeks

starter kit to full build

What you get

  • Working production system, deployed to your AWS account
  • Your domain logic on top of the primitive library
  • Observability, governance, and compliance from day one
  • Source access, and well-defined, permissive escape hatches
  • Capabilities briefing on what is built, and extensions to bridge the rest, by us or by you
  • Handover documentation and runbooks
  • Training for the engineers who will inherit it

Best fit

Companies that need a production system in weeks and do not want to spend a year on foundations.

Book a consultation
fig. ii·c6 deliverables

Operate

We keep it running, patched, and evolving. Or we hand it over and step back.

Ongoing

retained, renewed annually

What you get

  • On-call cover and incident response
  • Platform upgrades, security patches, infrastructure maintenance
  • Quarterly architecture and cost review
  • Continued feature delivery against your roadmap
  • Air-gapped and GovCloud deployment options
  • A defined exit, whenever you want to take it in-house

Best fit

Teams running in production who would rather grow their product than staff a platform group.

Book a consultation
fig. ii·d6 deliverables

Self Service

You license the platform and do the building yourself. We hand you the documentation and tooling, and stay out of the way.

Your pace

platform license, your engineers

What you get

  • Platform license and runtime binaries
  • Comprehensive documentation for every primitive
  • Configurable, bootstrapped Functory deployments
  • Deployment runbooks for your own AWS account
  • The same escape hatches every engagement gets
  • A clear path into Discovery or Build if you want us alongside

Best fit

Engineering teams who want the platform's head start and prefer to do the building themselves.

Explore the docs
III
The questions

Questions we get.

Plain answers, no discovery deck.

01
Why is there no price list?
Because every engagement is scoped to an outcome, and the honest number depends on your domain, your compliance surface, and how much already exists. Discovery is deliberately fixed and small so you get a real quote before committing to a build. If you want a rough range before committing to Discovery, ask on the call and we will give you one.
02
Who owns the code you write?
You do. The system runs in your AWS account, the domain code is yours outright, and the platform underneath it is licensed to you. If you end the relationship, the system keeps running.
03
What is the platform's role if this is a services engagement?
It is why we can quote weeks instead of quarters. Identity, commerce, workflows, search and 200+ primitives are already built and tested, so the engagement focuses on what makes your product unique. You get the benefit of the platform without becoming a platform team.
04
Can our own engineers take over?
That is the intended end state. Build engagements include handover documentation, runbooks, and training. Operate exists for teams who would rather not staff that function, not because the handover is difficult.
05
Do you take equity or a revenue cut?
No. We invoice for engineering work and license the runtime. Your revenue, your data, and your customer relationships are not ours.
06
How are AWS costs billed?
Directly by AWS, to your AWS account. We have no reseller arrangement and do not mark up infrastructure. During Discovery we build a cost projection against your actual workload, so you see the number before you commit.
07
Can you deploy into GovCloud or an air-gapped account?
Everything we deploy is AWS-native and provisioned as infrastructure-as-code, so the deployment model is the same one your own account uses. We ship the runtime binaries, the infrastructure stacks, and a deployment runbook, with no outbound connections required from your environment.

Coda

Start with a conversation.

Tell us what you are building.

Thirty minutes, no deck. We will tell you whether this is work we should take on, and what it would take.

Book a consultationSee the platform first