Project types
The six project types Eved offers — what each one provisions and which Febasi product it connects to.
A project in Eved provisions a concrete resource: an authentication tenant, an API endpoint, an automation workflow, a database connection. The project type you pick determines what gets provisioned, which dashboard tabs you see, and which Febasi product the project connects to.
The six types
| Type | What it provisions | Product backing it |
|---|---|---|
| Authentication | An identity tenant: users, roles, permissions, tokens, CORS, IP allowlist, JWT secret. | Febasi Auth |
| Service | An API surface with routes, types, and access control. | Eved-native (in development). |
| Application | A frontend application linked to the tenant's auth and services. | Eved-native (in development). |
| Database | A managed database connection with schema and migration tooling. | Eved-native (in development). |
| Automation | A visual workflow that connects services, databases, and external APIs. | Eved-native (in development). |
| Integration | A connector to a third-party service. | Eved-native (in development). |
Authentication is the most mature today. The others are progressively rolling out — when their docs land, they will share this same project-creation flow.
Creating a project
From inside a workspace, choose + New project, pick the type, and follow the type-specific wizard. The wizard captures everything the project needs at creation time; the rest is configurable from the project dashboard afterwards.
The Authentication wizard is documented in Auth project.
What every project gets
Regardless of type, every project has:
- A project page that becomes the operational dashboard for that type.
- Members who can see and operate it (inherited from the workspace, optionally narrower).
- Settings for the type-specific resources.
- Activity log of changes and significant actions.