FirstSite guidance
Don’t Build These on FirstSite
FirstSite can build websites, business applications, SaaS products, AI applications and even simple games.
But it isn't designed to build everything.
Here are the projects you should not build primarily on FirstSite.
1. AAA-Style 3D Games
Don't try to build the next Call of Duty or GTA on FirstSite.
Projects requiring:
- Advanced 3D rendering
- Complex physics
- Huge game worlds
- Sophisticated shaders
- Large downloadable assets
need a dedicated game-development environment.
Browser-based card, puzzle, strategy, management and lightweight 2D games are a different story.
2. Serious Real-Time Multiplayer Games
Avoid games where success depends on millisecond-level synchronization between large numbers of players.
That includes:
- Competitive FPS games
- Battle royale games
- MMORPG infrastructure
- Complex real-time physics
- Large-scale matchmaking
Turn-based and asynchronous multiplayer applications are much more suitable.
3. Ultra-Low-Latency Systems
Some systems can't afford normal web application latency.
Examples include:
- High-frequency trading
- Real-time securities execution
- Industrial control
- Network control infrastructure
If milliseconds are mission-critical, you need specialized infrastructure.
4. Heavy Computing Infrastructure
Don't use FirstSite to provide the underlying compute for:
- Training large AI models
- Hosting large AI models
- GPU compute
- Scientific simulations
- Large-scale video processing
- Massive data-processing pipelines
But there's an important distinction:
Building an AI application on FirstSite is fine.
Connect your application to the specialist infrastructure through an API.
5. Infrastructure Software
FirstSite builds applications. It isn't designed to build the infrastructure applications run on.
Don't use it to build:
- Operating systems
- Database engines
- Container orchestration
- Cloud hosting platforms
- Distributed storage systems
- Networking infrastructure
6. Deep Hardware or OS-Level Software
FirstSite is web-first.
It's not the right environment for:
- Device drivers
- Antivirus software
- OS-level utilities
- Deep Bluetooth applications
- Hardware-control software
- Kernel extensions
These require access that normal web applications don't have.
7. Safety-Critical Control Systems
Don't use FirstSite as the core software controlling systems where failure could cause physical harm.
Examples:
- Aircraft controls
- Medical-device controls
- Autonomous vehicle controls
- Industrial safety systems
- Critical infrastructure controls
You could still build the dashboard, reporting system or management portal around them.
The Difference Is Simple
FirstSite is designed to build the application layer.
It's not intended to replace specialized infrastructure underneath it.
Build an AI app.
Don't build the GPU infrastructure.
Build a trading dashboard.
Don't build a high-frequency trading engine.
Build an industrial management portal.
Don't build the safety system controlling the machinery.
Build a browser game.
Don't build the next AAA 3D game engine.
The FirstSite Rule
If it can reasonably run as a modern web application, FirstSite is worth considering.
If you're building heavy infrastructure, specialized hardware software, millisecond-critical systems or high-performance computing, use technology designed specifically for that job.
Otherwise, start with what you want to build and see how far you can get.
Know what FirstSite is good at—and use specialist technology when the problem genuinely requires it.