Guida Enterprise
Development alpha. Enterprise brings source code, draft tests, record design and data-product operations into a browser-based Console. Early evaluation uses a prepared installation with operator support. Docker images and Windows packages are publicly downloadable; a complete self-service installation bundle is in preparation.
Try the interactive careers exercise before installing anything. Its downloadable code and tutorial connect the browser exercise, a local command-line run and the Studio workflow.
Start with your setup path to understand what you need. If an installation is ready for you, follow early testing and your first draft test.
Your route through the guide
Section titled “Your route through the guide”| What you need | Where to go |
|---|---|
| Understand the product and choose a task | Practical use cases |
| Arrange an installation and sign in | Installation and first access |
| Understand what runs where | Components and terminology |
| Make a first successful edit and test | First-draft tutorial |
| Understand records, mappings and releases | From draft to data product |
| Connect a runner or Node | Execution hosts |
| Connect a coding assistant or understand AI setup | AI and coding assistants |
| Maintain the evaluation or diagnose a failure | Operations and troubleshooting |
| Find packages and understand alpha access | Downloads, Docker images and alpha availability |
What you work with
Section titled “What you work with”| Concept | What it means in your work |
|---|---|
| Workspace | The scope in which you can access source drafts, products and operations. Your identity must be authorized for it. |
| Source and extractor | A description of where data comes from, its expected input/output and the code that collects it. |
| Draft | Saved, editable authoring work. You can inspect and test it before preparing a release. |
| Record structure and mapping | The fields your product needs and how source output supplies them. |
| Data product | The selected records and API definition that you prepare, review, publish and activate. |
| Campaign | Managed execution work whose progress you follow in operations. |
A saved draft, a successful test and a published product have different effects. Saving preserves your edits. Testing executes saved code and returns results. Preparing a release starts a separate review and publication process. An API preview uses samples; it does not mean those records have been accepted and served.
How the pieces fit together
Section titled “How the pieces fit together”You use Studio in the Enterprise Console to edit sources, run tests and shape records. The Enterprise API handles authorized requests and coordinates server state. The local alpha setup uses a separate Windows development draft runner to execute trusted saved drafts, including headed browser tests.
Enterprise Node is a separate execution host for enrolled, authorized Enterprise work. It is different from the development draft runner and from generic Guida Node, which serves standalone automation through Remote Ops. Guida Complete is a separate Windows desktop app; you do not need to learn its entire interface before trying Studio. Guida Control is also a separate operator app and is not the Enterprise Console.
Start with the authoring workflow
Section titled “Start with the authoring workflow”Edit a source, run its saved draft and inspect the result. When a test fails, follow the error back to the code, correct it and run again. Reuse a successful sample to design record fields and mappings before preparing a release.
AI assistance is optional and experimental. You can complete the tutorial and continue building sources manually. See AI and coding assistants for setup and current integration status.
Choose your first task
Section titled “Choose your first task”- Try the interface: use the first draft tutorial to edit code, see a result, introduce a failure and correct it.
- Arrange an evaluation: use the early-testing checklist to agree on access, a test workspace and support with the installation operator.
- Understand the product: see the Enterprise overview for the Studio workflow and a screenshot from the development installation.
- Follow future work: the roadmap separates provider testing and further authoring work from the existing Studio foundation.
See alpha availability for packages, access and the next steps for Enterprise.