See your own Architectural Drift in 14 days.
A free assessment of your software architecture, run with one named contact at StackRails. You get a one-page Architectural Drift Report PDF for your exec team, plus a portal and AI chat on your real architecture: the map of your services and dependencies, live architecture documentation, technical debt, and the full issue report. The deep findings land around Day 10. The report is yours either way.
The 14-day timeline.
No surprises. No open-ended sales cycle. Five named milestones.
- 1
Day 0
Access role provisioned. Hosted POV runs in StackRails EU under a GitHub App. VPC POV runs in your AWS, Azure, or GCP account under a cloud access role (IAM role, managed identity, or service account). 5 minutes hosted, 30 minutes VPC.
- 2
Act 1: the map (week 1)
StackRails draws your cloud environment for the first time: services, dependencies, and ownership mapped from your real architecture. Zero effort for your team. Your contact checks in by email; no daily meetings unless you want them.
- 3
Act 2: the intelligence (Day 10)
The deep dependency graph (including loosely-coupled event-bus subscribers), live documentation, the full AI-architectural-review issue report (technical debt, drift, scalability), and an AI chat you can ask "what breaks if I change this?" The one-page Architectural Drift Report PDF anchors it for your exec team.
- 4
Day 10
Sixty-minute review meeting. We walk the findings together on your data, live in the portal.
- 5
Day 14
Paid proposal with a 30-day signature window. Or the report stays with you and the relationship parks until you're ready.
What the assessment is, and what it isn't.
It is
- Production scope
- On your real architecture
- One named contact at StackRails
- Time-boxed to 14 days
- Free
It isn't
- A self-serve trial
- A synthetic sandbox
- Co-mingled with a competing vendor on the same repos
- Open-ended on dates
Architectural Drift Report: what's in it.
A one-page exec PDF, plus a hands-on portal and AI chat on your own architecture. Yours either way.
- One-page Architectural Drift Report PDF: the exec anchor
- Portal with a map of your cloud environment: services, dependencies, and ownership drawn for the first time
- Deep dependency graph, including loosely-coupled event-bus subscribers most teams can't map themselves
- Full AI-architectural-review issue report: technical debt, drift, and scalability, ranked
- Live architecture documentation: what your new joiners would have on day one
- AI chat on your own architecture: ask "what breaks if I change this?" and questions about your infra and code
Your source stays in your environment, and your code never trains a model.
Common questions.
What if our procurement cycle is longer than 14 days?
We also run a 2-Month Extended POC for teams that need post-generation and pull-request enforcement validated before contract. Talk to your contact at the Day-10 review meeting.
Who owns the Drift Report?
You do. The report is yours either way, whether you proceed or not.
Can we run this alongside another vendor?
Not on the same repos in the same window. The assessment is exclusive on the codebase under evaluation.
Where does this run?
Hosted in StackRails EU under your KMS, or in your own AWS, Azure, or GCP account under a cloud access role. Your choice at kickoff.