Build it ourselves

What we don't build ourselves, we don't have

Principle

At NFCtron, we believe that if we don't build something ourselves, then we don't have it. This principle means we prefer our own solutions over dependencies on external services and products that we cannot fully control.

What It Means in Practice

Own Development

• We prefer our own implementations over third-party solutions
• We control the entire stack - from database to frontend
• We have full control over functionality and security

Minimizing Dependencies

• We limit dependencies on external services that we cannot influence
• When we need an external service, we consider whether we can build it ourselves
• External dependencies are acceptable only if they are critical and cannot be replaced

Long-term Perspective

• We build for long-term sustainability
• Own solutions mean we're not dependent on changes in external services
• We have the flexibility to adapt to our needs

When to Use External Solutions

External solutions are acceptable when:

• They are critical for system operation and cannot be replaced
• They are standard and widely used (e.g., cloud infrastructure)
• The cost of own development would be disproportionately high
• They are tools, not our core business

Examples

✅ Own Solutions

• NFCtron Hub - own management system
• Ticket system - own implementation
• API and integrations - own architecture

⚠️ External Solutions (when necessary)

• Cloud infrastructure (AWS, Azure, etc.)
• Basic tools (Git, CI/CD platforms)
• Standard libraries and frameworks

Related Principles

• Marathon mode - we build for the long term