Frequently asked questions
Direct answers to questions about Ordnami's pricing, product, security, and procurement — without scheduling a sales call.
Pricing & billing
- What's actually in Pro at $49?
- Up to 25 team members, 50 specs/month, all integrations (Linear, Slack, GitHub, Confluence, Notion), custom instructions, and 5 concurrent sessions. The $49 stays flat through 25 users; above 25 it's $4/seat, capped at 200 users. See /pricing for the full plan grid.
- What happens if my team exceeds 25 users mid-month?
- Pro tier prices each seat above 25 at $4/seat/month, prorated to the day they're added. So a team that grows from 25 to 30 users mid-month sees a small prorated bump on the next invoice. No retroactive charges, no surprise reclassification to Enterprise.
- Do you offer annual prepay discounts?
- Not on the Pro tier — pricing is $49/mo flat regardless of billing cadence. Enterprise customers (200+ users) can negotiate annual terms with a discount during procurement. Email billing@ordnami.ai with your team size if you'd like an annual quote.
- What payment methods do you accept?
- Credit card (any major card) via Stripe on the Pro tier. Enterprise tiers support invoiced billing on Net 30 terms — ACH, wire transfer, or check. Procurement portals are supported on Enterprise engagements.
- Is there a free trial?
- Yes — every plan includes a 14-day free trial with no credit card required. The Starter tier is permanently free (1 user, 5 specs/month, Linear + Slack only) so you can keep exploring after the trial without entering payment info.
- Can I cancel or downgrade anytime?
- Yes. Pro is month-to-month and you can downgrade to Starter or cancel from the Settings → Billing page at any time. Cancellation takes effect at the end of the current billing period — no proration of partial months, no early-termination fees.
Product & integrations
- Which integrations do you support today?
- Linear, Jira, Slack, GitHub, Confluence, and Notion are first-class integrations with both read access (context for specs) and write-back (spec output where applicable). The product roadmap includes broader integration support; check the dashboard's Connections screen after sign-up for the current list.
- Does Ordnami work with my code repository?
- GitHub is the primary code-repository integration today. We don't support GitLab or Bitbucket at this time; both are on the roadmap. If GitLab or Bitbucket is a procurement gate for your team, email hello@ordnami.ai — we prioritize integration work based on customer demand.
- What about my issue tracker?
- Linear is the primary issue-tracker integration with full read/write support. Jira and GitHub Issues are also supported. If your team uses a different tracker, email hello@ordnami.ai — we prioritize integration work based on customer demand.
- Can Ordnami access my Confluence, Notion, or Google Docs knowledge base?
- Confluence and Notion are supported with read access (Confluence supports auto-update for spec output). Native Google Docs integration is on the integration roadmap based on customer demand — email hello@ordnami.ai if it's a procurement gate for your team.
- How does Ordnami learn my team's conventions?
- Two ways. First: the codebase you connect — Ordnami's specs are grounded in real file paths, ticket IDs, and Slack threads, so the agent's outputs naturally follow your team's actual patterns. Second: the Custom Instructions field on the Pro tier lets you encode style preferences, naming conventions, and spec-format expectations the agent applies consistently.
- What AI model does Ordnami use?
- Anthropic's Claude models, accessed via AWS Bedrock. Bedrock-routed inference does not train Anthropic's foundation models on your inputs — that's contractually guaranteed by AWS Bedrock's terms. See /for/security for the full data-handling explanation.
- Does Ordnami make changes to my code, or only read it?
- Read-only by default. Ordnami opens files, cites specific lines, and pulls context — it doesn't push, write, or modify code in any repository. Output specs are written back to Linear, GitHub issues, or Confluence pages only on integrations where you've explicitly granted write scope.
- How current is the codebase context?
- Ordnami queries the repository via the GitHub API with a short cache lifetime to respect GitHub's rate limits, so the codebase context is typically current within a few minutes of your latest commits. There's no weekly batch index; the context refreshes naturally as the agent works.
Security & compliance
Short answers below; for the full security walkthrough see /for/security.
- Is Ordnami SOC 2 certified?
- Not yet. Our SOC 2 Type II audit window opens Q4 2026, with the Type II report available in 2027. Our controls and data-handling practices are designed to meet SOC 2 Type II standards today. See /for/security for the full statement and how to evaluate Ordnami for enterprise procurement before the report is final.
- Can I sign a DPA?
- Yes — our standard Data Processing Agreement is available on request from security@ordnami.ai. It covers GDPR Article 28 processor obligations, CCPA service-provider terms, and standard contractual clauses for international transfers. Sub-processor list included.
- Where is my data stored?
- AWS us-east-1 (N. Virginia) by default, encrypted at rest (AES-256) and in transit (TLS 1.2+). EU residency and additional US regions are available on Enterprise tiers. Workspaces are segregated per-tenant at the database (row-level security) and storage (per-tenant prefixes) layers.
Procurement & legal
Short answers below; for the finance lead's walkthrough see /for/finance.
- Do you provide an MSA, SLA, and DPA?
- MSA and DPA: templates are in finalization with outside counsel; draft language is available now from billing@ordnami.ai for evaluations that need it. SLA: Enterprise tiers include a written SLA with target uptime and response-time commitments. Pro tier operates on a best-effort basis; service health is monitored 24/7 and incident communications go directly to affected customers via email.
- What are your standard terms?
- Pro tier: month-to-month, credit card billed via Stripe, cancel anytime, 14-day free trial. Enterprise tier: typically annual contracts with Net 30 invoicing, custom SLA terms, and procurement-portal compatibility. Standard payment terms are 30 days from invoice on Enterprise.
- Do you work with procurement portals?
- On Enterprise engagements, yes — we support standard procurement portals. Email billing@ordnami.ai with your portal of choice and we'll confirm integration. Pro tier billing goes through Stripe directly and doesn't route through procurement portals.
- Are you a W-9 vendor?
- Yes. Ordnami, Inc. is a U.S.-incorporated vendor; W-9 is provided as part of standard vendor onboarding. Email billing@ordnami.ai if you need it before signing up.
- Who do I contact for procurement?
- billing@ordnami.ai for MSA, DPA, W-9, invoicing, payment terms, and procurement-portal setup. security@ordnami.ai for security questionnaires, controls walkthroughs, and DPA-adjacent technical questions. Typical first-response is one business day.
Team & company
- Who built Ordnami?
- Ordnami is built by a small founding team of engineers who spent years inside product orgs writing the kind of specs Ordnami now produces. We started Ordnami because the gap between vague tickets and specs engineers can actually ship from cost us — and our teams — too much time. See /about for more on the company.
- Where are you based?
- Ordnami, Inc. is incorporated in the United States and operated by a remote-first team. We don't disclose specific office addresses but our corporate address for procurement and legal purposes is provided as part of standard vendor onboarding.
- How big is the team?
- Small and growing. We're deliberately staying lean while we build out the product surface and onboard early customers — the goal is to be the team that gets you a thoughtful answer in one business day, not a routed support ticket.
- Are you VC-backed?
- Ordnami is operated by a U.S.-incorporated company with private financing. We don't share investor or funding-stage specifics publicly at this stage; if you need to verify financial stability for procurement, we can provide a Dun & Bradstreet number and standard vendor documentation through billing@ordnami.ai.
Implementation & onboarding
- How long does setup take?
- Setup typically takes under 30 minutes for the basic case — sign up, connect Slack and Linear via OAuth, point at a GitHub repository, and start writing specs. Adding Confluence and Notion takes another few minutes each. There's no infrastructure to provision, no separate install, and no IT ticket required for the standard SaaS path.
- Do you offer onboarding help?
- Yes — every paid plan includes onboarding support. Pro customers get async support via email (typical first-response: same business day) and the in-app help center. Enterprise customers get a named onboarding contact and a kickoff session with the engineering team to tune custom instructions.
- Is there training for my team?
- The product is designed to be usable without training — most teams figure out the basic spec-writing loop in their first session. For larger rollouts, our help center at /help has step-by-step guides for each integration, and Enterprise customers can request a recorded walkthrough or live training session via security@ordnami.ai.
- What's the typical time-to-first-value?
- Most teams write their first useful spec within the first day of setup — that's the spec where Ordnami's codebase grounding catches a file the engineer had forgotten about, or pulls in a Slack thread that changed the scope. The compounding value (consistent style, faster onboarding for new engineers, fewer scope arguments) shows up over the first 30 days.
- Can I test Ordnami in a sandbox before connecting my real codebase?
- Email security@ordnami.ai to discuss your sandbox requirements — we'll work with your team to match the right evaluation path to your procurement context.
Didn't see your question?
Email hello@ordnami.ai and we'll get back to you, usually within one business day.