Workspace Structure

API Reference: Environments

In FoxNose, Organizations, Projects, and Environments form the foundation of your workspace structure, each playing a distinct role in content management, access control, and billing. Understanding these entities is essential for effectively organizing your workflows, managing access, and structuring your data.

Organization

Organizations are the highest-level entity in FoxNose. When you register in the system, an organization is automatically created for you, and you become the owner of that organization.

Key Characteristics

• Billing Entity: Each organization has its own subscription plan
• Flexible Plans: You can choose different plans for different organizations, giving you flexibility in managing costs and features
• Top-Level Access: Organization owners have full access to all projects and environments within their organization

Transferring Ownership

If you need to transfer ownership of your organization to another user, you can do so by contacting our support team at support@foxnose.net. The support team will guide you through the necessary steps to complete the transfer securely.

Project

A project isolates data for specific tasks or applications. Organizations can manage multiple projects to separate data and workflows as needed.

Regional Configuration

When creating a project, you select a region for data storage to minimize network latency and comply with local data regulations. Choose the region closest to your target audience unless specific legal requirements apply.

Data Privacy Mode

For projects in the European Union, you can enable Data Privacy Mode to ensure GDPR compliance:

• EU-Only Routing: All non-EU requests are routed through EU servers
• EU CDN Nodes: Only EU-based CDN nodes are used for content delivery
• Flexible Configuration: Can be toggled at any time
• Performance Consideration: May increase latency for non-EU users

Enable this only for sensitive EU citizen data where compliance is critical.

Environments

An environment is an isolated space within a project, designed for specific stages of content management and testing. Each environment has its own unique host-specific URLs, ensuring isolated access to data via the Flux API.

Production Environment

By default, a production environment is created when the project is set up:

• Optimized Performance: Designed for handling high loads and live operations
• Single Instance: Only one production environment per project
• Protected: Cannot be deleted to ensure data safety

Additional Environments

You can create additional environments for development and testing:

• Safe Testing: Experiment without impacting live data
• Isolated Access: Each environment has its own unique URLs
• Flexible Creation: Create as many test environments as needed

Resource Usage

All environments share project resources:

• Database Storage: All environments consume database storage from your organization's quota
• API Requests: Requests across all environments (production and test) count toward your organization's usage limits