Question 1

Why did iTmethods rebrand?

Accepted Answer

iTmethods rebranded to better reflect our evolution from a DevOps platform to a comprehensive AI infrastructure provider. Our product name 'iTmethodsONE' was an internal version identifier that didn't capture the AI-native capabilities we deliver. 'Forge' better represents what we do: forging mission-critical applications with speed, security, and sovereignty. Additionally, we're expanding with Reign (the AI Governance Platform) and Reign for Life Sciences (powered by BioCompute.ai), requiring a coherent brand architecture.

Question 2

What is the iTmethods platform?

Accepted Answer

iTmethods builds the Trust Layer for Enterprise AI. Two products built for regulated industries: Reign (the AI Governance Platform) and Forge (Managed Runtime + Modern DevOps). Reign governs. Forge runs. Reign for Life Sciences (powered by BioCompute.ai) is the deep-specialty configuration for pharma, biotech, and CROs. All share a common principle: enterprises shouldn't have to choose between innovation velocity and regulator-grade evidence.

Question 3

When did the rebrand happen?

Accepted Answer

The iTmethods rebrand launched publicly on January 19, 2026. All external materials including our website (itmethods.com), LinkedIn presence, and marketing materials reflect the Reign + Forge product architecture as of this date.

Question 4

Is iTmethods being acquired or changing ownership?

Accepted Answer

No. iTmethods remains an independent, founder-led company. Paul Goldman remains Founder & CEO. We are profitable, growing 20% year-over-year, and the rebrand reflects our expansion, not any change in ownership, control, or business direction.

Question 5

What is iTmethods Inc.?

Accepted Answer

iTmethods Inc. is the legal corporate entity that remains unchanged. Reign, Forge, and BioCompute are product brands under the iTmethods corporate umbrella. All contracts, certifications, and legal relationships remain under iTmethods Inc.

Question 6

How should I refer to your company?

Accepted Answer

You can refer to us as 'iTmethods' (the company) or by specific product names: 'Reign' (AI Governance Platform) and 'Forge' (Managed Runtime + Modern DevOps). For the platform collectively, use 'the iTmethods platform' or 'Reign and Forge. The Trust Layer for Enterprise AI.' Reign for Life Sciences (powered by BioCompute.ai) is the deep-specialty configuration for life sciences workloads.

Question 7

Does anything change with my service?

Accepted Answer

No. Your service, contract, pricing, support, team, tools, and configurations all remain exactly the same. The only thing changing is the name we use to describe the platform you're already using. Your login credentials, portal access, SLAs, and dedicated account team remain unchanged.

Question 8

Do I need to sign a new contract?

Accepted Answer

No. Your existing contract remains fully valid. The legal entity (iTmethods Inc.) hasn't changed. We may add a simple rider on your next renewal noting 'iTmethodsONE d/b/a Forge' for clarity, but this doesn't require any immediate action or negotiation.

Question 9

Will my costs change due to the rebrand?

Accepted Answer

No. This rebrand has zero impact on your pricing. Your current contract pricing, including any negotiated discounts or growth tiers, remains in full effect through the contract term and beyond.

Question 10

Do I need to update anything on my end?

Accepted Answer

No action required from you. You don't need to update internal documentation, procurement systems, or vendor lists immediately. When you naturally update those materials during annual reviews, you can refer to us as 'iTmethods Forge' or simply 'Forge.'

Question 11

What if my team still calls it iTmethodsONE?

Accepted Answer

That's completely fine. We expect the transition to happen naturally over time. Both 'iTmethodsONE' and 'Forge' refer to the same platform, so there's no urgency to retrain your team. Use whatever terminology feels most natural for your organization.

Question 12

Will my invoices change?

Accepted Answer

Your invoices may continue to show 'iTmethodsONE' for a few billing cycles while we update our billing system. This is purely cosmetic. Your service, pricing, and payment terms remain unchanged. We'll communicate once invoices fully reflect the new Forge branding.

Question 13

Will my account manager change?

Accepted Answer

No. Your dedicated account team remains your team. Same people, same relationships, same level of support. The rebrand doesn't affect staffing or account assignments.

Question 14

How do I explain this rebrand to my internal stakeholders?

Accepted Answer

Keep it simple: 'Our DevOps vendor iTmethods renamed their platform from iTmethodsONE to Forge. Nothing changes with our service, pricing, or support. Just a new name that better reflects their AI-native capabilities.'

Question 15

Are there any new certifications or compliance changes?

Accepted Answer

No. All existing certifications (SOC 2 Type II, HIPAA, FedRAMP In Process, ISO 27001) remain valid and unchanged. The legal entity (iTmethods Inc.) that holds these certifications hasn't changed. We continue all compliance programs without interruption.

Question 16

Will the portal URL change?

Accepted Answer

The primary portal remains accessible at portal.itmethods.com. We may add forge-branded aliases in the future, but your current bookmarks and integrations will continue working indefinitely.

Question 17

How long has iTmethods been in business?

Accepted Answer

iTmethods has 21 years of deep expertise in enterprise DevOps and regulated industries. Our longevity reflects our commitment to stability and customer success.

Question 18

Who leads iTmethods?

Accepted Answer

Paul Goldman is the Founder & CEO of iTmethods. The company remains founder-led with a focus on sustainable growth and customer-first values.

Question 19

What industries does iTmethods serve?

Accepted Answer

iTmethods primarily serves regulated industries including healthcare, financial services, government, life sciences, and enterprise technology. Our products are designed for organizations where security, compliance, and data sovereignty are non-negotiable.

Question 20

Where can I learn more about the rebrand?

Accepted Answer

Visit our website at itmethods.com for the latest information about Reign, Forge, and BioCompute. You can also contact your account manager or reach out at contact@itmethods.com for any specific questions.

Question 21

What is Forge?

Accepted Answer

Forge is iTmethods' Managed Runtime providing 55+ modern DevOps tools with enterprise compliance. All tools are pre-integrated in a fully managed, compliant-by-design environment. For AI governance, see Reign. Our dedicated Enterprise AI Governance platform.

Question 22

How does Forge differ from iTmethodsONE?

Accepted Answer

Forge IS iTmethodsONE. Same platform, new name. The rebrand reflects our evolution: Forge is the Managed Runtime (55+ managed tools), while AI governance capabilities are now part of Reign, our dedicated Enterprise AI Governance platform. All your existing tools, configurations, and workflows remain exactly the same.

Question 23

What tools are included in Forge?

Accepted Answer

Forge includes 55+ enterprise DevOps and AI tools including: Atlassian suite (Jira, Confluence, Bitbucket), GitHub Enterprise, Jenkins, JFrog Artifactory, SonarQube, and many more. All tools are pre-integrated, fully managed, and compliance-ready.

Question 24

What is the Reign AI Gateway?

Accepted Answer

The Reign AI Gateway is the enterprise AI access layer that provides secure, governed access to AI models (OpenAI, Anthropic, Google, AWS Bedrock) with full audit trails, PII protection, policy enforcement, and cost controls. It eliminates shadow AI while enabling safe AI adoption. The AI Gateway is now part of the Reign platform.

Question 25

What is MCP and why does it matter?

Accepted Answer

MCP (Model Context Protocol) is an open standard for connecting AI systems to enterprise data and tools. With 97M+ monthly SDK downloads, MCP is becoming the standard way AI agents access enterprise systems. Reign AI Gateway is MCP-native and offers a unified control plane for all MCP traffic with enterprise compliance, policy enforcement, and cost attribution. Regardless of who operates the servers.

Question 26

What deployment options does Forge offer?

Accepted Answer

Forge offers three deployment options: Multi-tenant SaaS (fastest, 1-2 weeks), Dedicated Cloud (your own isolated environment, 2-4 weeks), and On-Premises/Air-Gapped (complete sovereignty, 6-8+ weeks). All options include the same 55+ tools and full management.

Question 27

Is Forge compliant with SOC 2?

Accepted Answer

Yes. Forge (iTmethods Inc.) maintains SOC 2 Type II certification with annual audits. This covers all multi-tenant and dedicated cloud deployments. Audit reports are available under NDA for enterprise customers.

Question 28

Is Forge HIPAA compliant?

Accepted Answer

Yes. Forge supports HIPAA compliance for healthcare customers. We sign Business Associate Agreements (BAAs) and provide HIPAA-ready configurations. Many healthcare organizations use Forge for their DevOps and AI needs.

Question 29

What is Forge's FedRAMP status?

Accepted Answer

Forge is currently FedRAMP In Process at the Moderate impact level. We're working toward full FedRAMP authorization to serve federal government customers. Contact us for the latest timeline and interim authorization options.

Question 30

How fast can I get started with Forge?

Accepted Answer

Multi-tenant deployments can be live in 1-2 weeks. Dedicated cloud environments typically take 2-4 weeks. On-premises and air-gapped deployments require 6-8+ weeks depending on your infrastructure requirements.

Question 31

Does Forge support SSO?

Accepted Answer

Yes. Forge supports enterprise SSO via SAML 2.0 and OIDC. We integrate with all major identity providers including Okta, Azure AD, Ping Identity, and OneLogin. SSO configuration is included in all enterprise plans.

Question 32

What SLA does Forge provide?

Accepted Answer

Production SLAs are documented per engagement and reviewed quarterly. SLA targets, incident history, and remediation procedures are available under NDA.

Question 33

Can I migrate from my current DevOps tools to Forge?

Accepted Answer

Yes. Our Migration Factory team specializes in tool migrations with zero downtime. We've successfully migrated organizations from on-premises Jira, Jenkins, GitHub Enterprise, and other tools to Forge. Migration services are available as professional services.

Question 34

Does Forge include Atlassian tools?

Accepted Answer

Yes. Forge includes fully managed Atlassian suite: Jira Software, Jira Service Management, Confluence, and Bitbucket. We handle all licensing, upgrades, security patches, and optimizations. Many customers consolidate their Atlassian spend through Forge.

Question 35

Can I use Forge with GitHub?

Accepted Answer

Yes. Forge supports both GitHub Enterprise Cloud and GitHub Enterprise Server. We can manage your GitHub instance as part of your Forge environment, or integrate with your existing GitHub deployment.

Question 36

What AI models does Reign support?

Accepted Answer

Through the Reign AI Gateway, Reign supports all major AI models: OpenAI (GPT-4, GPT-4o), Anthropic (Claude), Google (Gemini), AWS Bedrock, and Azure OpenAI. You can also connect custom or self-hosted models.

Question 37

How does Forge handle security?

Accepted Answer

Forge implements defense-in-depth security: encrypted data at rest and in transit, network isolation, vulnerability scanning, penetration testing, 24/7 security monitoring, and incident response. All tools are hardened according to CIS benchmarks.

Question 38

Can I get dedicated support?

Accepted Answer

Yes. Forge offers multiple support tiers including 24/7 premium support with dedicated account teams, named engineers, and guaranteed response times. Enterprise customers get direct access to senior engineers.

Question 39

How does Forge integrate with CI/CD pipelines?

Accepted Answer

Forge provides fully managed CI/CD through Jenkins, GitHub Actions, and GitLab CI. All pipelines run in secure, isolated environments with artifact management (JFrog), code quality scanning (SonarQube), and security testing integrated.

Question 40

What is Reign?

Accepted Answer

Reign is iTmethods' Enterprise AI Governance platform. It provides a control plane for managing AI usage across your organization. From discovery and policy enforcement to cost optimization and compliance reporting.

Question 41

What problem does Reign solve?

Accepted Answer

Reign addresses the growing 'Shadow AI' challenge. As AI adoption accelerates, many organizations find themselves with ungoverned AI usage and unexpected costs. Reign provides visibility into AI usage across your organization, enforces policies, and helps bring shadow AI under governance. Typically within 30 days.

Question 42

How quickly can Reign be deployed?

Accepted Answer

Reign can go from shadow AI to governed AI in 30 days. Discovery and initial deployment take 1-2 weeks, with full policy enforcement and reporting live within a month. This is significantly faster than building governance in-house.

Question 43

What AI platforms does Reign govern?

Accepted Answer

Reign governs all major AI platforms: ChatGPT/OpenAI, Anthropic Claude, Google Gemini, Microsoft Copilot, AWS Bedrock, Azure OpenAI, and custom/self-hosted models. If your employees use it, Reign can govern it.

Question 44

How does Reign help prevent shadow AI?

Accepted Answer

Reign helps organizations govern AI access by working alongside your existing security infrastructure. The platform routes authorized AI traffic through your controlled environment. To prevent shadow AI, organizations typically implement firewall rules to block direct AI provider URLs or deploy endpoint policies. Reign provides the visibility and reporting to identify gaps in your AI governance.

Question 45

What policies can Reign enforce?

Accepted Answer

Reign enforces customizable policies including: data classification restrictions, PII/PHI blocking, prompt injection prevention, response filtering, usage quotas, department budgets, model access controls, and audit requirements. Policies are defined in plain language.

Question 46

Does Reign support compliance reporting?

Accepted Answer

Yes. Reign generates evidence for SOC 2, HIPAA, GDPR, and industry-specific regulations. All AI interactions are logged with full audit trails, user attribution, and policy violation tracking.

Question 47

Can Reign control AI costs?

Accepted Answer

Yes. Reign provides complete visibility into AI spend across all platforms and users. You can set department budgets, usage quotas, and receive alerts when thresholds are approached. Customers typically discover 2-3x more AI spend than expected.

Question 48

Is Reign a standalone product?

Accepted Answer

Yes. Reign is a standalone AI governance platform that works independently of Forge. You can use Reign to govern AI usage even if you're not using Forge for DevOps. However, Reign and Forge integrate seamlessly for customers using both.

Question 49

How does Reign protect sensitive data?

Accepted Answer

Reign intercepts AI prompts before they reach external models, automatically detecting and blocking PII, PHI, financial data, source code, and custom-defined sensitive patterns. Data never leaves your control perimeter unless explicitly allowed by policy.

Question 50

What industries benefit most from Reign?

Accepted Answer

Reign is designed for regulated industries: healthcare (HIPAA), financial services (SOX, SEC), government (FISMA), and any organization with data protection requirements. Any enterprise concerned about AI governance benefits from Reign.

Question 51

Can I use Reign with Forge?

Accepted Answer

Absolutely. Reign and Forge are designed to work together. Forge provides governed AI tools for development teams, while Reign extends governance across your entire organization. Together, they provide complete AI governance from code to corporate.

Question 52

How is Reign different from enterprise DLP?

Accepted Answer

Traditional DLP is reactive and pattern-based. Reign is AI-aware, understanding context, intent, and semantic meaning. Reign specifically understands AI interactions, prompt patterns, and model behaviors. Something generic DLP tools can't do.

Question 53

Does Reign require agents on endpoints?

Accepted Answer

Reign offers flexible deployment: browser extension for individual monitoring, network proxy for transparent interception, or API integration for programmatic access. Choose the deployment model that fits your security architecture.

Question 54

Where can I learn more about Reign?

Accepted Answer

Visit the Reign page for detailed information about Reign's capabilities, pricing, and implementation. You can also request a demo to see Reign in action with your specific use cases.

Question 55

What is BioCompute?

Accepted Answer

BioCompute is iTmethods' Trust Layer for Enterprise AI in Life Sciences, available at BioCompute.ai. It provides AI infrastructure designed for FDA 21 CFR Part 11 requirements. For pharmaceutical, biotech, and medical device companies who need complete data sovereignty.

Question 56

What does data sovereignty mean for AI in life sciences?

Accepted Answer

Data sovereignty for AI means complete control over your data, models, and infrastructure. For life sciences, this means your proprietary research, patient data, and competitive insights never leave your controlled environment. Critical for FDA submissions and IP protection. BioCompute.ai delivers this as the Trust Layer for Enterprise AI in regulated science.

Question 57

Is BioCompute FDA compliant?

Accepted Answer

BioCompute is designed to support 21 CFR Part 11 requirements for electronic records and signatures. Our infrastructure supports the validation, audit trails, and documentation needed for FDA submissions. Specific applicability depends on your use case.

Question 58

What life sciences use cases does BioCompute support?

Accepted Answer

BioCompute supports drug discovery, clinical trial optimization, genomics analysis, regulatory document automation, pharmacovigilance, and research data management. Any life sciences AI workload requiring sovereignty and compliance.

Question 59

How is BioCompute deployed?

Accepted Answer

BioCompute is deployed in your controlled environment: dedicated cloud, on-premises, or air-gapped. Unlike public AI services, your data never leaves your perimeter. Deployment typically follows a 60-day regulatory pathway.

Question 60

What is the 60-day regulatory pathway?

Accepted Answer

BioCompute follows a structured 60-day implementation: Discovery (weeks 1-2), Deployment (weeks 3-4), Validation (weeks 5-6), and Production (weeks 7-8+). This ensures proper validation and documentation for regulated environments.

Question 61

Can BioCompute run custom AI models?

Accepted Answer

Yes. BioCompute supports both commercial AI models and your custom-trained models. You can run proprietary drug discovery models, fine-tuned clinical models, or any specialized life sciences AI while maintaining complete sovereignty.

Question 62

How does BioCompute handle patient data?

Accepted Answer

BioCompute processes patient data within your controlled environment with infrastructure designed to support HIPAA requirements. Data is encrypted at rest and in transit, access is role-based with full audit trails, and no data is shared with external AI providers.

Question 63

Is BioCompute suitable for small biotech?

Accepted Answer

Yes. BioCompute serves organizations from early-stage biotech to large pharma. Pricing scales with usage, and you can start with specific use cases before expanding. Many customers start with regulatory document automation.

Question 64

Does BioCompute integrate with lab systems?

Accepted Answer

Yes. BioCompute integrates with common life sciences systems including LIMS, ELN, CDMS, and research data platforms. We support standard APIs and can develop custom integrations for proprietary systems.

Frequently Asked Questions

Popular Questions